[rabbitmq-discuss] Is there ever a need for a federation and a cluster?

Langston, Jim Jim.Langston at compuware.com
Wed Jan 4 18:35:08 GMT 2012

This is the one that caught my attention, since the federation description
is what I currently have , two clusters, each independent, but need to
exchange the messages. The are on the same LAN , just have different jobs
to do. This was the place I saw that federation was the way to do it, I
maybe combining the clusters into one would do it as well, but I didn't see
where that was doable, even given that everything is identical as far as


On 1/4/12 1:25 PM, "Simon MacMullen" <simon at rabbitmq.com> wrote:

>That's basically it.
>See a bit more discussion at: http://www.rabbitmq.com/distributed.html
>Cheers, Simon
>On 04/01/12 18:22, Michael Cumings wrote:
>> I'm in the process of setting up multiple clusters, each cluster is in a
>> different data center separated by WANs.  I don't want to try to cluster
>> across a WAN connection, but there are some messages that I want to be
>> able to route to both locations.
>> On Wed, Jan 4, 2012 at 12:20 PM, Langston, Jim
>> <Jim.Langston at compuware.com <mailto:Jim.Langston at compuware.com>> wrote:
>>     Hi all,
>>     Given a scenario where the entire environment is identical for
>>     rabbitMQ (same servers, OS's , RMQ versions Š etc) , would there
>>       be a need to have the environment configured for using both
>>     as a cluster, and as a federation ?
>>      From what I've gathered so far, before experimenting, it seems that
>>     unless there is some sort of mixed environment, clustering is the
>>     to go.
>>     What about if there are two different clusters, w/ different
>>brokers and
>>     exchanges ? Would you want to use a federation between them ?
>>     Thanks,
>>     Jim
>>     The contents of this e-mail are intended for the named addressee
>>     only. It contains information that may be confidential. Unless you
>>     are the named addressee or an authorized designee, you may not copy
>>     or use it, or disclose it to anyone else. If you received it in
>>     error please notify us immediately and then destroy it.
>>     _______________________________________________
>>     rabbitmq-discuss mailing list
>>     rabbitmq-discuss at lists.rabbitmq.com
>>     <mailto:rabbitmq-discuss at lists.rabbitmq.com>
>>     https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>Simon MacMullen
>RabbitMQ, VMware
>rabbitmq-discuss mailing list
>rabbitmq-discuss at lists.rabbitmq.com

More information about the rabbitmq-discuss mailing list