Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/user-manual/amqp-address-federation.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ On the remote peer a queue binding is created on the federated address which wil
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.
For a more complete reference of the AMQP Address Federation configuration elements refer to the xref:amqp-federation-configuration-glossary.adoc[AMQP Federation Configuration Glossary]

image::images/amqp-federation-address-concept.png[]

Expand Down
2 changes: 2 additions & 0 deletions docs/user-manual/amqp-broker-connections.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -464,6 +464,8 @@ The broker connection federation configuration consists of one or more policies
</broker-connections>
----

For a more complete reference of the AMQP Federation configuration elements refer to the xref:amqp-federation-configuration-glossary.adoc[AMQP Federation Configuration Glossary]

=== Address federation

Address federation can be thought of as full multicast over a set of loosely coupled brokers.
Expand Down
1 change: 1 addition & 0 deletions docs/user-manual/amqp-queue-federation.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,7 @@ image::images/amqp-federation-queue-concept.png[]

Queue federation can be configured 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 queue on the opposing broker instance.
When configured for dual federation messages can migrate back and forth between brokers depending on capacity and available local consumers, this back and forth message flow can be reduced by ensuring that the federation policy uses a pull when space is available configuration which will only pull a batch of messages from the remote if the local queue does not already have a backlog.
For a more complete reference of the AMQP Queue Federation configuration elements refer to the xref:amqp-federation-configuration-glossary.adoc[AMQP Federation Configuration Glossary]

== Common Queue Federation Topologies

Expand Down