[rabbitmq-discuss] Application Architecture Question (topic routing + fanout broadcasting)?

Andrew Barringer abarringer at gmail.com
Tue Aug 14 16:02:45 BST 2012


Thanks for the reply!

In retrospect tutorial five does seem blindingly obvious for this use case.
Not sure how I missed that.


On Tue, Aug 14, 2012 at 8:04 AM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> On 14/08/12 13:39, m.luchak at smartasking.com wrote:
>> The exchange to exchange binding is IMHO the way to go.  You can create
>> "user" exchanges bound to the origin exchange(s) with the binding keys
>> that you require and temp Qs that bind to the "user" exchanges...
> I don't think e2e is necessary here...
>  -----Original Message-----
>> From: "Andrew Barringer" <abarringer at gmail.com>
>> [...]
>> The hard part is with a topic exchange/queue only one subscriber is
>> going to get an item when it hits the exchange/queue.
> That is incorrect. Exchanges route messages to all queues with bindings
> that match the message. Is that not clear from our documentation, in
> particular the tutorials? The topic routing tutorial (
> http://www.rabbitmq.com/**tutorials/tutorial-five-**python.html<http://www.rabbitmq.com/tutorials/tutorial-five-python.html>)
> even has an example illustrating the routing of messages to multiple queues.
> So simply give each subscriber their own queue and bind it to the exchange
> with the topic patterns describing their interests.
> Regards,
> Matthias.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120814/f9c4c6e8/attachment.htm>

More information about the rabbitmq-discuss mailing list