[rabbitmq-discuss] Scaling Throughput with Highly Available Queues

[Richard Raseley]

Matthias,

The relevance lies in the fact that the design of this particular
application component relies on a single highly available queue bound to a
single exchange. My thought (which you've mostly confirmed) was that if I
create multiple clusters with mirrored configurations (e.g. same exchanges,
queues, users, etc.) and place those in a single load balanced pool I will
be able to scale my performance (while maintaining high availability for
all messages) whereas if I add additional nodes to a cluster I will not -
as all operations will happen via the mater queue process which resides on
exactly one node.

Thank you very much for your quick replies.

Regards,

Richard




On Tue, Mar 19, 2013 at 2:30 PM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> On 19/03/13 21:16, Richard Raseley wrote:
>
>> Sorry, I meant to say the master queue process. Can you comment on my
>> previous question assuming that correction?
>>
>
> Yes, all queue operations go via the queue's master.
>
> However, I fail to see what relevance that has to your question about
> scaling throughput via either adding nodes to a single cluster or creating
> new clusters. In either case you are only going to get additional
> scalability at the queue level by having more than one queue and
> distributing those queues them over the available nodes.
>
> Matthias.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130319/e506c94a/attachment.htm>