12

I've built this sample: Getting Started With RabbitMQ in .net, but made 2 programs:

  • one-publisher
  • one-subscriber

I'm using BasicPublish to publish and BasicAck to listen as in example. If I run one publisher and several subscribers-on every "send message" from publisher- only one subscriber gets it. So that there is some order (as subscribers were started) in which publisher sends message to subscribers, and I want to send one message to all subscribers. What is wrong with that sample? May be you can provide working sample of publisher/subscribers message exchange via RabbitMq?

DanielV
  • 2,076
  • 2
  • 40
  • 61
0x49D1
  • 8,505
  • 11
  • 76
  • 127

3 Answers3

14

The example you link to uses simple queueing without an exchange, which ensures that only a single consumer will handle the message. To support pub/sub in RabbitMQ, you need to first create an Exchange, and then have each subscriber bind a Queue on that Exchange. The producer then sends messages to the Exchange, which will publish the message to each Queue that has been bound to it (at least with the simple Fanout exchange type. Routing can be achieved with Direct and Topic exchanges.)

For a Java sample (which could be converted to C# pretty easily) please see here.

Edit: Updated .Net version can be found here

Noctis
  • 11,507
  • 3
  • 43
  • 82
dlev
  • 48,024
  • 5
  • 125
  • 132
4

I've added a new tutorial about this Getting Started With RabbitMQ in .net

DanielV
  • 2,076
  • 2
  • 40
  • 61
longhairedsi
  • 3,133
  • 2
  • 28
  • 28
  • Thank you - so far your example is the only one I've seen that does asynchronous subscriptions in .NET. Calling Invoke on a delegate seems "retro" - is there a better way? – TrueWill Oct 12 '11 at 16:37
1

There are also some official sources now.

0x49D1
  • 8,505
  • 11
  • 76
  • 127