The Erlang VM or How I Started Loving Parallel Progamming
summary
BEAM implements message passing, isolated lightweight processes with under 300 words per process heaps/stacks, per-process garbage collection and cooperative preemption by counting reductions, and supports hot code loading plus OTP primitives (gen_server, supervisors, FSMs). Messages copy via an mbuf and two inboxes to minimize locking; iolists give constant-time concatenation for sending big binaries. Klarna runs this VM in production and reports handling exponential traffic growth for years with automated supervisor restarts keeping services up.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:33Topic
- 9:47Erlang Internals
- 17:50Concurrency Model
- 22:56Process Director
- 28:29Monitors
- 29:26Supervision
- 31:28Trycatch
- 33:21Interactive Shell
- 35:13Interactive Shell Examples
- 37:59OTP Libraries
- 40:17Model as Services
- 42:51Most important aspect of Erlang
- 43:32Sponsor Dona
- 46:11Questions
related talks
01h 01mThe Erlang Ecosystem
43mConcurrency Oriented Programming in a Modern World
10mBack to the Future
49mBEAM Concurrency in Action
42mThe Soul of Erlang and Elixir
40mComparison and Commentary on "Application Operating System"
52mConcurrency Oriented Programming in a Modern World
42mConcurrency Oriented Software