From 76d36282ed9eb842c964a6e164fbf0e503bfdbb1 Mon Sep 17 00:00:00 2001 From: Auri Munoz Date: Fri, 11 Oct 2024 11:14:46 +0200 Subject: [PATCH] Add clarification about how composite service discovery works. --- docs/docs/service-discovery/composite.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/docs/service-discovery/composite.md b/docs/docs/service-discovery/composite.md index 51e2f791..7060a03f 100644 --- a/docs/docs/service-discovery/composite.md +++ b/docs/docs/service-discovery/composite.md @@ -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" \ No newline at end of file