Multiple Subscribers forwarding it to the same Queue - Azure

Question

I'm looking to utilize the same queue for multiple subscriptions,

Just wondering if this a good practise, and what are pro's and con's of this design?

if messages are processed in the same way and state with topicID is not something you care about when processing that message in the queue then I see no problem in this approach. Though usually you have 1 publisher and 1 or many subscribers, that is the usual model but it does not mean you cannot do this. — Hassan Raza, Sep 14 '20 at 08:50

score 1 · Accepted Answer · answered Sep 14 '20 at 18:02

It depends on what do you do. There are a few use-cases for a centralized queue topology:

Have a single source of messages for scale-out. Rather than having N number of subscription listeners and exhausting broker connections, you have only one queue to listen to and scale-out on.
Centralized dead-letter queue - instead of handling dead-letter queue per subscription, you consolidate all dead-lettered messages in a single queue to consume from. Those messages will have information about their original source if that's needed for decision making.
Migration scenario - when your old topic/subscription needs to be drained off the messages before it can be decommissioned.

1 Answers1