This is an automated email from the ASF dual-hosted git repository. jbertram pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/artemis.git
commit 0a37571b5f091650470e1aca9dc1084dc3ae7fe1 Author: Timothy Bish <[email protected]> AuthorDate: Wed Dec 10 17:59:08 2025 -0500 ARTEMIS-5797 Add additional clarification on address hub and spoke Explain a bit more of the linkages between nodes when demand is applied on a spoke. --- docs/user-manual/amqp-address-federation.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/user-manual/amqp-address-federation.adoc b/docs/user-manual/amqp-address-federation.adoc index 61cacdbb03..0344af2fc9 100644 --- a/docs/user-manual/amqp-address-federation.adoc +++ b/docs/user-manual/amqp-address-federation.adoc @@ -120,6 +120,7 @@ Note the `max-hops=4` in this case since there are five brokers in the diagram, Another configuration that allows consumers on brokers to read messages produced on any other broker peer is a hub and spoke configuration. In this configuration spoke brokers connect to a central hub and message traffic between the spokes passes through that hub broker which centralizes communication and allows the spokes to only need to know about one other broker, the hub broker. +When demand exists on any of the spokes they create a federation consumer link to the hub, this in turn causes the hub to create federation consumer links to each of the spokes where the address exists regardless of the presence of a producer on those spokes in order to ensure that when a producer arrives the messages that it sends reach the other spokes with attached consumers (this is shown on diagram at `spoke 3`). image::images/amqp-federation-address-hub-spoke.png[] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
