5

I've started working with RabbitMQ and my use case is quite simple - producers putting messages on queues to to processed by consumers. Each message is processed by at most one consumer and messages are directed from producer to consumer based on queue name.

Direct exchanges seem perfectly fine for this and the default exchange is a direct exchange.

Are there any reasons (performance, management, permissioning etc.) to not use the default exchange and create your own one instead? For example, I will be using high-availability queues (https://www.rabbitmq.com/ha.html) and wasn't sure if there would be any negative impact on the cluster if all the HA queues were on the default exchange as opposed to a different exchange?

user783836
  • 3,099
  • 2
  • 29
  • 34

1 Answers1

1

With the default exchange you gain performance, since there's almost no routing logic involved, but then you end up coupling your publishers to your consumers, which is kinda an anti-pattern in messaging.

At the same time if your concern is performance, I doubt RabbitMQ's routing performance would be the first problem you encounter. Queue paging, queue synchronization over a network in the case of HA, and so on, seems like things I would worry about when caring for performance.

old_sound
  • 2,243
  • 1
  • 13
  • 16
  • Thanks. I wasn't worried about performance per se (it was just an example) but more if there are any good reasons to not use the default exchange if I want direct routing. For example, I recently found out that there are limitations around the default exchange and federation. – user783836 Oct 13 '15 at 09:51
  • I don't see a reason to use the deafult exchange unless you are doing something like RPC – old_sound Oct 13 '15 at 11:52