Skip to content

Commit

Permalink
Merge pull request #956 from aureamunoz/add-composite-clarification
Browse files Browse the repository at this point in the history
Add clarification about how composite service discovery works.
  • Loading branch information
aureamunoz authored Oct 14, 2024
2 parents 7981737 + 76d3628 commit 087a833
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion docs/docs/service-discovery/composite.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,9 +38,14 @@ For each service that should consist of multiple services, configure the service
quarkus.stork.serviceB.service-discovery.type=...
```


Remember to define the services that make up your composite service.

Be aware that Stork doesn't work as a standalone service discovery cluster.
Instead, it processes composite configurations—meaning it handles multiple configurations that may use different service discovery implementation.
For each specific configuration, Stork delegates the service discovery task to the appropriate service discovery provider.
If one of these providers doesn't respond or fails, it affects Stork's ability to resolve that specific configuration, but it doesn't mean Stork itself is faulty;
it relies on the performance of the service discovery systems it’s configured to work with.

These are all the parameters of the composite service discovery:

--8<-- "target/attributes/META-INF/stork-docs/composite-sd-attributes.txt"

0 comments on commit 087a833

Please sign in to comment.