CODEWITHSUNDEEP
rebus
jondow
jondow

Reputation: 724

Rebus pub-sub system. Process each message by one and only one subscriber

With rebus, I'd like to be able to publish from one application, and subscribe from multiple applications, where each message only gets processed by one subscriber in a round robin, as described here: https://www.rabbitmq.com/tutorials/tutorial-two-dotnet.html

Is this possible with rebus?

Upvotes: 2

Views: 918

Answers (1)

mookid8000
mookid8000

Reputation: 18628

Yes, but the words "publish" and "subscribe" are confusing here, because it's not "Publish/Subscribe" as described in the literature, because pub/sub pretty much means that you do not care how many listeners there are.

What you want, is to send a message, and then you want the sent messages distributed among multiple consumers.

With Rebus, that is definitely possibly. However, the way you do it may depend slightly on which transport, you are using(*)

Most transports have pretty good support for the competing consumers pattern, where you simply start multiple processes, probably running on multiple machines, that consume messages from the same queue.

This way, each message gets processed exactly once, and each consumer will receive messages at a rate that suits that particular consumer.

(*) MSMQ is not good at distributing load when multiple processes are taking messages off of the same queue, especially not when the processes are running on other machines than where the queue is.

Upvotes: 1

Related Questions