tabish121 commented on code in PR #6101:
URL: https://github.com/apache/artemis/pull/6101#discussion_r2608293198


##########
docs/user-manual/amqp-address-federation.adoc:
##########
@@ -0,0 +1,136 @@
+= Address Federation
+:idprefix:
+:idseparator: -
+:docinfo: shared
+
+Address federation can be thought of as full multicast over the connected 
brokers.
+Every message sent to address on `Broker-1` will be delivered to every queue 
bound to that address on that broker, but also will be delivered to the 
matching address on `Broker-2`, `Broker-3` ... `Broker-N` and all the queues 
bound to that address.
+
+Address federation creates consumers that read messages from the matching 
address on the remote peer when demand is detected on a local address that 
matches a specific federation address policy. On the remote peer a queue 
binding is created on the federated address which will store and forward 
messages sent to that address back to the initiating broker. Once a message 
arrives at the federation address consumer on the initiating broker it is then 
published into the local address which routes the message into each of the 
queues bound to that address.
+
+Address federation can be configured to operate in a single direction between 
peers or can configured to operate in both directions between peers allowing 
message to flow in both directions delivering messages to consumers on either 
broker that were sent to the matching address on the opposing broker instance.
+
+image::images/amqp-federation-address-concept.png[]
+
+== Common Address Federation topologies

Review Comment:
   fixed



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to