Update RabbitMQ now!
summary
Alerts about patched CVEs including ROBOT and an Erlang client-auth bypass plus fixed AMQP 1.0 memory exhaustion drive the urgency; a shovel bug that re-delivered orders after broker restart shows real risk. Upgrades cut memory and IOPS pain (one customer sees big memory drops), enable Quorum queues and streams for message safety and cost savings, and benefit from Erlang JIT performance gains. Migration is practical: convert classic v1 → v2 queues, automate with APIs/Terraform, and batches hit ~200 upgrades/day.
AI-written summary · about
chapters (14)
- 0:00RabbitMQ upgrades intro
- 1:54Why upgrade RabbitMQ now
- 3:19Security fixes in RabbitMQ
- 5:31Message safety improvements
- 9:12Performance gains from upgrade
- 11:43Observability and new features
- 15:03Migrating to new features
- 18:04Making upgrades a habit
- 21:41Common objections to upgrades
- 24:12Message broker upgrade history
- 25:41Seamless upgrade future
- 28:56Q&A: Downgrade processes
- 30:03Q&A: Release frequency
- 31:08Q&A: Customer update resistance
related talks
21mWhy does RabbitMQ stop and what can be done about it
39m101 ways to break your RabbitMQ
35mHow to Safely and Reliably (...) While Maintaining 100% Uptime
48mA Beginner's Guide to Inter-Service Messaging
34mProxying Rabbits For Stability & Reliability
48mBEAM all the things
50mOps issues
24mMigration from On-Prem Messaging System to The Cloud