[rabbitmq-discuss] One Producer, Many Consumers, Many physical nodes

[Bell, Paul M.]

Michael and Alvaro,

Thank you both. That's good news.

Please let me follow-up with some finer grained aspects:

Am I right to think that the "one producer, one queue, many consumers on different computers" model would allow "even" distribution of messages? I don't want each message duplicated for each consumer. Rather, the fan-out should partition the entire message set with each consumer getting a subset thereof.

When a consumer pulls a message from the queue, is there a way to leave that message in queue? If so, can queue elements be updated in-place, e.g., with "status" info about the state of the work that the message (task) represents?

Thanks again.

-Paul


-----Original Message-----
From: rabbitmq-discuss-bounces at lists.rabbitmq.com [mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Michael Bridgen
Sent: Thursday, January 12, 2012 10:12 AM
To: rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] One Producer, Many Consumers,Many physical nodes

On 01/12/2012 03:05 PM, Bell, Paul M. wrote:
> All,
>
> I am new to Rabbit and am trying to understand how best to deploy it in
> a given system.
>
> I envision a single producer writing to a single queue, and multiple
> consumers pulling from this single queue. The wrinkle here is that these
> consumers can be on different physical computers.
>
> Can this be done with Rabbit and, if so, can someone explain the several
> approaches to it?

Yes, many clients is what RabbitMQ is designed for. The queue is hosted
at the server and the clients interact with it over the network.

You may wish to run through the tutorials at
http://rabbit.mq/getstarted.html

-Michael


>
> ------------------------------------------------------------------------
>
>
> ATTENTION: -----
>
> The information contained in this message (including any files
> transmitted with this message) may contain proprietary, trade secret or
> other confidential and/or legally privileged information. Any pricing
> information contained in this message or in any files transmitted with
> this message is always confidential and cannot be shared with any third
> parties without prior written approval from Syncsort. This message is
> intended to be read only by the individual or entity to whom it is
> addressed or by their designee. If the reader of this message is not the
> intended recipient, you are on notice that any use, disclosure, copying
> or distribution of this message, in any form, is strictly prohibited. If
> you have received this message in error, please immediately notify the
> sender and/or Syncsort and destroy all copies of this message in your
> possession, custody or control.
>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> 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



ATTENTION: -----

The information contained in this message (including any files transmitted with this message) may contain proprietary, trade secret or other  confidential and/or legally privileged information. Any pricing information contained in this message or in any files transmitted with this message is always confidential and cannot be shared with any third parties without prior written approval from Syncsort. This message is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any use, disclosure, copying or distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or Syncsort and destroy all copies of this message in your possession, custody or control.