Competing-Consumers Messaging Pattern in Azure Service Bus

3
votes

I'm just getting started with Windows Azure Service Bus (Topics & Queues) and I'm trying to implement a Competing-Consumers messaging pattern.

Essentially, I want to have a set of message Producers and a set of message Consumers. Once a message is produced, I want the first available Consumer to process the message. No other Consumers should get the message.

Is there a way to do this in Azure?

3
azureazureservicebus
What kind of/how much work is behind each message? What are your time constraints? - Simon Opelt
@Simon Ideally Consumers would start processing a message within 10-30ms of the time the message is Produced. If Producers are out-pacing Consumers, I will add more Consumers to meet demands. - JoeGeeky

3 Answers

3
votes

You probably don't want Topics then, but rather Brokered Messaging.

You can emulate Topic-like functionality in Brokered Messaging by using the message's Label and/or Content Type properties along with the PeekLock receive mode.

6
votes

Simple. Just make two (or more) receivers that concurrently receive from a single queue and you're done. Any retrieved message goes to exactly one of those receivers since the cursor over the mesasage log is advanced as a message is taken. Competing consumers are an inherent capability of a networked queue so there's really nothing special needed.

If you need the opposite - each message goes to each consumer - you make a subscrioption per consumer which gives you an isolated cusor over the message log that can move independent of other receivers. For kicks, you can obviously also have competing consumers on a subscription.

Clemens

3
votes

Topics are a feature of brokered messaging, but are a one-to-many "publish/subscribe" pattern. Queues are one-to-one message communication. So yes, it sounds like you should simply use queues. Also see http://msdn.microsoft.com/en-us/library/hh689723(VS.103).aspx.