Concurrency Oriented Programming in a Modern World
summary
Explains Erlang’s concrete claims: the BEAM VM spawns lightweight processes in microseconds to spawn using a few bytes each, supports selective receive and linked processes with supervisors, and makes fault recovery a system-level pattern — let it crash as a restart strategy. Shows real results: WhatsApp hit 2 million TCP connections (and later Phoenix 2M WebSockets on AWS) by tuning FreeBSD and the VM. Contrasts BEAM’s immutable, no-shared-memory design for scale and resilience with JVM’s shared-memory focus on speed.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:17Concurrency oriented programming
- 6:18Hard at work developing Erlang
- 7:39The main ideas
- 18:37Why is this relevant today?
- 22:42Concurrency vs parallelism
- 24:52BEAM vs. JVM
- 27:31Erlang & WhatsApp
- 29:17Phoenix Framework
- 39:48Erlang ecosystem
- 42:30Outro
related talks
52mConcurrency Oriented Programming in a Modern World
51mThe Erlang VM or How I Started Loving Parallel Progamming
42mConcurrency Oriented Software
40mComparison and Commentary on "Application Operating System"
43mConcurrency Abstractions for Application Security
39mConcurrent Languages are Functional
37mCrashing BEAM applications
35mDiving into Erlang is a one-way ticket