Let me start this off by saying RabbitMQ is a great piece of software. It excels in areas where other messaging stacks are either too cumbersome or overly complicated. Plus, it’s written in wacky Erlang.
With all of its merits, however, a common hurdle is trying understand its RabbitMQ’s exchange, queue, and routing key terminology. Only adding to the confusion, the documentation states routing key functionality depends on the exchange type being used. Developers trying to adopt RabbitMQ looking for a durable and simple message stack are often left feeling a bit betrayed.
For many users, the exchange, queue, and routing key concepts go beyond what will ever be needed. It’s important to understand how they work, and how powerful they are, but it’s just as important that the extra moving parts aren’t a deterrent.
Read more »