RabbitMQ: Longevity, Limitations, and Continued Popularity

Hello everyone, I am Jun.

RabbitMQ is a well‑known message queue that many developers have used; I first used it in 2016. Although it is an old‑standing system, it has not been eliminated, and this article explores why.

Outdated Aspects

Release History

RabbitMQ was first released in 2007, giving it over 16 years of history.

Niche

RabbitMQ is considered niche for two reasons: it is written in Erlang, a less‑common language with a steep learning curve, and it uses the AMQP protocol, which many mainstream queues do not support.

The AMQP protocol defines concepts such as:

Connection: a network connection, usually long‑lived.

Channel: a lightweight connection built on a Connection; one Connection can have many Channels.

Exchange: receives messages and routes them to bound Queues.

Binding: a virtual link between an Exchange and a Queue.

Routing Key: a rule that determines how an Exchange routes messages to Queues.

These concepts are absent in many mainstream queues like Kafka or RocketMQ, making RabbitMQ relatively niche.

Performance

RabbitMQ does not use zero‑copy techniques such as MMAP or Sendfile for message persistence, which contributes to lower performance.

It provides mirrored queues for master backup, which adds extra hops for producers and consumers, reducing throughput compared with RocketMQ (hundreds of thousands) and Kafka (millions).

Popularity

Despite its age and performance drawbacks, many companies still choose RabbitMQ during technology selection, as observed from my experience and interview candidates.

Continuous Updates

RabbitMQ is still actively maintained, with frequent releases; for example, several versions were released in 2023.

Having been around since 2007, it is a battle‑tested system with abundant learning resources and stable performance.

Easy Operations

RabbitMQ is lightweight and claims to work out‑of‑the‑box. Deploying it on Docker requires only three commands:

docker pull rabbitmq:3.8.2-management

mkdir /var/lib/rabbitmq

docker run -d --name rabbitmq3.8.2 -p 5672:5672 -p 15672:15672 -v `pwd`/data:/var/lib/rabbitmq --hostname myRabbit -e RABBITMQ_DEFAULT_VHOST=my_vhost -e RABBITMQ_DEFAULT_USER=admin -e RABBITMQ_DEFAULT_PASS=admin --privileged=true

This simplicity greatly reduces learning and operational costs.

Flexible Routing

Based on AMQP Exchanges, RabbitMQ offers four routing types:

Direct Exchange – routes messages to a queue based on a Routing Key.

Fanout Exchange – broadcasts messages to all bound queues.

Topic Exchange – uses patterns with * (single word) and # (zero or more words) in routing keys.

Headers Exchange – routes based on message headers, matching either all or any defined header pairs.

Examples of Topic and Headers routing are illustrated with diagrams in the original article.

Rich Client Support

RabbitMQ supports more client languages than most other queues, making integration easy for diverse systems.

Conclusion

Although RabbitMQ is an older system with modest throughput, its ease of deployment, flexible routing, extensive client libraries, and ongoing updates make it a popular choice for many medium‑scale applications.