[rabbitmq-discuss] Federated Exchange Upstream / Downstream Names

Tue Oct 8 13:32:23 BST 2013

Hi Michael,

I'm sorry-- I'm not sure I follow.

If I did use a topic exchange, and all brokers federated that same
exchange, then senders could specify the 'A', 'B', or 'C' in the routing
key, but... the consumers in 'A', 'B', and 'C' would still need to know
where they are ('A', 'B', or 'C') in order to bind their queue on the right
key.  Binding on '*.requests' would give them all traffic.

On the other hand, if each broker federated a *different* topic exchange,
then we're back in the original situation-- now binding on '*.requests'
would work, but the consumers would need to know where they are to bind
their queue to the right exchange.

Maybe I'm misunderstanding?

-Chris

On Mon, Oct 7, 2013 at 11:16 PM, Michael Klishin <michael at rabbitmq.com>wrote:

>
> On oct 8, 2013, at 12:53 a.m., Chris <stuff at moesel.net> wrote:
>
> > Imagine Broker A, Broker B, and Broker C.  Each federates a  direct
> exchange based on their name (for example, "A.requests", "B.requests",
> "C.requests").  Within each broker, however, I don't want consumers to need
> to know the broker name-- they should be able to bind their queues to
> (direct) exchange "Incoming.requests" and receive messages to "A.requests",
> "B.requests", or "C.requests" respectively.
>
> Have you considered using a topic exchange and bind as *.requests?
> Granted, prefix wildcards are not very efficient but if you only have a
> few dozens of queues
> bound you may even notice.
>
> MK
>
>
>
>
> _______________________________________________
> 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/20131008/58eb2f09/attachment.htm>