[rabbitmq-discuss] RabbitMQ message filtering based on routing key

Michael Klishin mklishin at gopivotal.com
Thu Feb 6 08:42:20 GMT 2014

On 6 Feb 2014, at 12:14, s_kan <sathish.kannath at wipro.com> wrote:

> "
> If you don't want a queue for each possible routing key you could aim
> for an intermediate granularity. Or partition consumers by capability,
> create a queue per partition and route messages according to the
> capabilities required for processing.
> "
> Any link/example/documentation for this method available?

One queue per capability is what tutorial 5 demonstrates. You can also
use 1 queue for users with ids 1-100 (say, partition A), another one for 101-200, and so on.
Your binding keys will look like users.partitions.a, users.partitions.b and so on.

For more sophisticated partitioning strategies see


Software Engineer, Pivotal/RabbitMQ

More information about the rabbitmq-discuss mailing list