OTP Has Done It
summary
Claims that OTP packages battle‑tested patterns into gen_server / gen_fsm / gen_event behaviors, with gen_server powering roughly 90% of production Erlang code; supervisors provide self‑healing trees used to run millions of concurrent users (a cited mobile game hit ~2.5M and never saturated the system). Uses include ETS for fast in‑memory key/value (note: owner process teardown destroys the table) and Mnesia for relational needs. Releases bundle the Erlang runtime, support hot upgrades via code_change, and enable configured failover standbys.
AI-written summary · about
chapters (15)
- 0:00Start
- 1:07The Otp Ecosystem
- 1:22The Principles That Otp Was Designed Around
- 4:38The Generic versus Specific Battle
- 10:17Applications Are Optionally Reusable
- 11:32Supervisors
- 12:55Restart Strategies
- 14:00Child Spec
- 15:09Common Design Patterns
- 16:25The Gem Server
- 19:47Interactions with Old Government Systems
- 25:03Access Modes
- 26:46Releases
- 34:19Recap
- 34:33Ephemeral Storage
related talks
48mZero Support in Production
34mUsing Distillery: Understanding OTP releases
44mConcurrency + Distribution = Scalability + Availability(...)
53mBuilding Performant Backends with Elixir
39mInstrumenting mayhem: functional chaos engineering
52mPerformance & Stability Anti patterns
40mInto Production
40mThe Benefits of Tierless Elixir/Potato for Engineering IoT Systems