Concurrency Oriented Programming in a Modern World
summary
Erlang/BEAM claims a concurrency-first model with isolated lightweight processes that take 1–3 microseconds to spawn a process, use per-process mailboxes and selective receive for message handling, and prefer a let it crash supervision pattern; Elixir and Phoenix bring those primitives to web stacks and the authors cite WhatsApp benchmarks of 2–3 million TCP connections on one machine as proof the approach scales while staying resilient and simple.
AI-written summary · about
chapters (12)
- 0:00Intro
- 2:41Concurrency oriented programming
- 7:22Hard at work developing Erlang
- 9:05The main ideas
- 30:08Why is this relevant today?
- 38:33BEAM vs. JVM
- 43:04Erlang & WhatsApp
- 45:41Phoenix Framework
- 47:25Erlang ecosystem
- 49:06Elixir
- 50:25Virding's 1st rule of programming
- 51:57Outro
related talks
43mConcurrency Oriented Programming in a Modern World
39mConcurrency Oriented Programming In A Modern World
42mConcurrency Oriented Software
49mBEAM Concurrency in Action
51mThe Erlang VM or How I Started Loving Parallel Progamming
01h 01mThe Erlang Ecosystem
10mBack to the Future
42mThe Soul of Erlang and Elixir