[Question] Multiple handlers for a queue separated by routing key

Hey,

Is it possible to do something like following with golevelup/rabbitmq within the same module?

@RabbitSubscribe({exchange:"any", queue:"user", routingKey:"key1"})
handleKey1() {
...
}

@RabbitSubscribe({exchange:"any", queue:"user", routingKey:"key2"})
handleKey2() {
...
}

[WonderPanda]

@eduscrakozabrus You have two handlers which are both bound to the same queue. This is an anti pattern. When you do this, all messages from both routing keys all end up in the same queue, but two handlers are connected to that queue so it is not deterministic which handler will receive the message.

The only way to safely re-use the same queue is if you add conditional logic inside the handler to check the contents of the message but that defeats the purpose of the entire library.

Just don’t re-use queues like this and you won’t have problems

[WonderPanda]

Queues in RabbitMQ are lightweight and they are intended to be purpose driven. There is no benefit to to reusing the same queue for multiple handlers. A typical application that’s properly leveraging RabbitMQ would have dozens if not hundreds or more queues.

A single RabbitMQ node could potentially handle tens of thousands of queues, see for example https://stackoverflow.com/a/22990200/1364771

If you really feel the need to do this (I’d be curious about your reasoning) you could have a single handler that receives all your messages through one queue. The handler could then do conditional processing based on the contents of the message itself.

There are no plans to try and implement the suggested functionality you’ve shown in your original comment as its generally an anti-pattern