BEAM all the things
summary
Migration at iwantmyname moves a complex Perl app onto Erlang/OTP and Elixir running on the BEAM with RabbitMQ and CouchDB, deployed as self‑contained releases and monitored with collectd and Graphite/Grafana. A zombie rabbit incident—RabbitMQ logging filling disk, losing the group leader and logs—gets diagnosed via remote shell and Recon/dbg and fixed by trimming logs; the system mostly works but exposes the need for an explicit error kernel, queued state machine design, backpressure, and watching the 95th percentile for latency.
AI-written summary · about
chapters (14)
- 0:00Intro
- 3:12Zombie Rabbit
- 8:12Running away
- 10:02Designer drug resistant
- 10:31Recovery
- 13:51State Machine
- 20:43Changes
- 28:11Failure
- 35:33Hanging Path
- 43:05Realtime monitoring
- 44:31Runtime
- 45:16Backlog
- 45:32Memory usage
- 46:06White debugging
related talks
41mDevOps' Swiss Army knife for the BEAM
21mWhy does RabbitMQ stop and what can be done about it
49mInto Production
39m101 ways to break your RabbitMQ
34mUpdate RabbitMQ now!
36mBring Back the Power of BEAM Deployments with DeployEx
18mRaspberry Pi Cluster with the Power of Elixir
22mLessons Learned from Scaling RabbitMQ in a High-Growth (...)