[rabbitmq-discuss] AWS clustering

[Glade Diviney]

That's the answer I need. Thanks, Francesco.

-Glade

On Wed, Sep 5, 2012 at 1:46 AM, Francesco Mazzoli <francesco at rabbitmq.com>wrote:

> Hi Glade,
>
> At Tue, 4 Sep 2012 20:01:38 -0700 (PDT),
> Glade wrote:
> > For a supposedly "just works" kind of service, that is just not good
> enough. I
> > can't have my ops people rolling out of bed to take action every time
> there's
> > a minor network glitch.
>
> Rabbit clustering is meant to be run on local networks and is not tolerant
> to
> "network glitches".  If you expect those, then don't use it.
>
> > So, I either need to provide a network that never becomes partitioned
> (does
> > such a network exist? Certainly not at AWS!), or I need to drop
> clustering and
> > have a single RabbitMQ server which won't scale, or I need to cobble
> together
> > some kind of automated supervisor which is certain not to handle all
> cases, or
> > I need to use a different messaging tool.
>
> Federation or shovel might fit your needs, see
> <http://www.rabbitmq.com/distributed.html> for an overview.
>
> --
> Francesco * Often in error, never in doubt
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120905/34a593b6/attachment.htm>