<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Wed, Jul 17, 2013 at 4:33 PM, Michael Klishin <span dir="ltr"><<a href="mailto:mklishin@gopivotal.com" target="_blank">mklishin@gopivotal.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">David van Geest:<br>
<div class="im"><br>
> I was wondering if it was possible to have a consumer subscribe to multiple queues, based on some kind of wildcard pattern.<br>
><br>
> For example, if all the queues in question were named "messages.<MAC>" where <MAC> is a MAC address, could a consumer subscribe to "messages.*"?<br>
<br>
</div>No, but you can set up message routing such that messages.<MAC> would go to the same queue.<br>
Then you can add as many consumers as you need to that queue.<br>
<br>
In other words, with RabbitMQ pattern matching happens at the routing stage, not message delivery.<br><br></blockquote><div><br></div><div>Michael, thanks for the reply. �The motivation for this question is that we would like to avoid one monolithic queue for all messages. �We're looking at clustering Rabbit, but even then your queue resides on one server, which could be a scalability problem if your number of message producers and thus message rate continually goes up.</div>
<div><br></div><div>We would like to scale our worker processes on the other end of the message queue(s) up and down as needed, without having the message producers know anything about it. �Any ideas on how to achieve this goal?</div>
</div>
</div></div>