wildcard binding with direct

[Raymond Rizzuto]

Is there any way to specify that I want to bind a queue to all routing keys on a direct exchange?  I know I can do that with a topic exchange using wildcards, but I don't need anything that flexible, and am worried about the performance of all that wildcard matching.

[Skrzypek, Jonathan]

In that case you can probably use a fanout exchange, you will receive everything regardless of the routing key.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Alvaro Videla]

There's no way to do that with a direct exchange. You could try what Skrzypek suggests.

Also see: http://www.rabbitmq.com/blog/2011/03/28/very-fast-and-scalable-topic-routing-part-2/

On Thu, May 21, 2015 at 5:59 PM Raymond Rizzuto <ray.r...@gmail.com> wrote:

Is there any way to specify that I want to bind a queue to all routing keys on a direct exchange?  I know I can do that with a topic exchange using wildcards, but I don't need anything that flexible, and am worried about the performance of all that wildcard matching.

--

[Raymond Rizzuto]

Thanks to both of you.

I can't use a fanout because not all queues will bind for everything.   I.e. Q1 may bind for X, Q2 may bind for Y and Q3 binds for everything, which may be a superset of { X Y}.

I'll go with topic.  My patterns will be pretty simple: X, Y and '#'.  I would imagine the matching for these should be pretty fast from the blog description.  Possibly '#' is optimized since no matching at all should be needed.