[rabbitmq-discuss] Help defining appropriate queue model
alexis at rabbitmq.com
Wed Mar 2 14:20:21 GMT 2011
The simplest way is probably as follows:
Note that each consumer has its own queue, which acts as a buffer on
behalf of that consumer. The downside of this is a slow consumer may
get several configuration updates at once, so it will need to discard
the earlier ones but should act on the latest.
On Wed, Mar 2, 2011 at 2:14 PM, Fabio Margarido
<fabiomargarido at gmail.com> wrote:
> Hi there,
> I'm about to use RabbitMQ in my first amqp project and am having a bit
> of difficulty identifying the necessary queues and exchanges.
> In our use case, there will be only one producer who publishes a
> message to the broker. This message represents configuration data.
> Then multiple consumers read the published configuration from the
> broker during their startup process, so it shouldn't happen very
> often. The message should remain in the queue after consumption so
> that the following consumers are able to read it. When some
> configuration data changes, the producer republishes it and alerts
> (possibly through some other queue) the consumers, who then read the
> configuration message again.
> I know this question isn't exactly related to RabbitMQ, but reading
> the AMQP spec didn't help much. Could anyone help me identify which
> exchange types, queue and message parameters I need for this to work?
> Thanks in advance.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss