February 8, 2007
RabbitMQ launched
LShift and CohesiveFT launched RabbitMQ on February 8, 2007 — an open-source AMQP message broker for reliable enterprise messaging.
What it was for
RabbitMQ routes messages between producers and consumers through exchanges and queues — decoupling microservicesAn architecture splitting applications into small independent services — each deployed and scaled separately., job workers, and event pipelines. It implements AMQP with clustering, persistence, and language clients for JavaA portable language running on the JVM — dominant in enterprise servers, Android, and big data., PythonA high-level language known for readability — dominant in data science, scripting, and web backends., and NodeNode.js — JavaScript on the server via an event-driven runtime built on V8.. Example: a web app publishes `order.created` events; fulfillment and email services consume them asynchronously.
Why it's here
RabbitMQ was the first production-grade open-source AMQP broker.
Why it mattered
It made message queues mainstream before KafkaApache Kafka — a distributed event streaming platform for high-throughput real-time data pipelines. and cloud pub/sub services.
What it solved
Applications coupled via direct HTTPHyperText Transfer Protocol — the protocol browsers use to request and receive web pages. calls could not absorb traffic spikes or retry failed work reliably.
Media
- ImageRabbitMQ
RabbitMQ, Public domain, via Wikimedia Commons
Related
- Apache Kafka open-sourcedJanuary 11, 2011
- Memcached releasedMay 22, 2003
- ZeroMQ project startedMay 2007