A love letter to messaging: Celebrating RabbitMQ's journey
summary
Covers RabbitMQ's evolution: Celery used for background tasks with RabbitMQ as default broker, hosted on CloudAMQP running 15,000 servers; version 3.6 introduces lazy queues wrote to disk to fix memory spike crashes; 3.8 adds quorum queues replicate across nodes for durability; streams (2021) give Kafka‑like persistent logs; MQTT support in 2023 lets CloudAMQP retire its own MQTT service; production users include Parkster, Visma, and a newspaper serving 65 million readers.
AI-written summary · about
chapters (20)
- 0:00Introduction and setup
- 1:53RabbitMQ’s origins in 2007
- 3:59Why message brokers matter
- 6:04Microservices with RabbitMQ
- 8:11E-commerce and scaling challenges
- 9:19Celery and background tasks
- 10:48From skeptic to RabbitMQ fan
- 12:13Routing keys and exchanges
- 14:41RabbitMQ management UI
- 15:01Memory leak and lazy queues
- 17:08Quorum queues and data safety
- 18:34Classic queues vs streaming
- 20:43MQTT support and consolidation
- 21:25RabbitMQ 4.0 and classic queues
- 21:46High-volume email delivery
- 22:27Manufacturing workflows
- 23:31WebSockets and real-time updates
- 24:58RabbitMQ in major companies
- 26:22Conclusion and community thanks
- 27:27Q&A session
related talks
49mA Love Letter to Messaging: Celebrating RabbitMQ's Journey
36mBeyond the Burrow: The Endurance of RabbitMQ
46mReal-world Examples of Message Queue Usage: Insights from RabbitMQ
32mRabbitMQ in Real Life - Tips and Tricks
39mReal World RabbitMQ: Exploring Practical Applications
19mUpdate from RabbitMQ Core Team
48mA Beginner's Guide to Inter-Service Messaging
19mRabbitMQ’s Common Issues & Misconceptions: A Support Perspective