An Overview of Message Queues: History, Concepts, and Comparison

The author shares a systematic summary of message queue technology, motivated by both personal study and practical project needs.

Message queue middleware dates back to the early 1980s when Vivek Ranadive envisioned a universal software bus; his company Teknekron released the first product, The Information Bus (TIB), which later attracted IBM and Microsoft, leading to the development of proprietary MQ solutions.

To overcome vendor lock‑in, the Java Message Service (JMS) was created as a common API, while the AMQP protocol was standardized in 2006 by Cisco, Red Hat, iMatix and others; RabbitMQ is a concrete implementation of AMQP.

Using a message queue decouples services, enables asynchronous processing, provides traffic‑shaping for bursty scenarios such as flash sales, and facilitates reliable log collection (e.g., Kafka for large‑scale logging), though it also introduces challenges like increased system complexity and the need for high availability.

The article compares four mainstream open‑source MQ products: ActiveMQ (mature but lower performance), RabbitMQ (high concurrency, low latency, Erlang‑based), RocketMQ (Alibaba‑backed, Java‑centric), and Kafka (ultra‑high throughput, low latency, ideal for big‑data and log aggregation, with occasional duplicate consumption).

In conclusion, the piece reviews the evolution and fundamentals of message queues and promises a follow‑up article focusing on RabbitMQ usage.