Thinking Erlang in a connected world
summary
Argues Erlang/OTP builds reliable, available, serviceable, secure systems by designing millions of isolated lightweight processes with message passing and supervision trees that contain and restart failures. Gives concrete examples: RabbitMQ and ejabberd use the VM, a live music service handled 16,000 concurrent connections with hot code upgrades, embedded images around 30–40MB, soft real‑time GC per-process, distribution and ports for safe C/Rust integration, and yearly releases with two‑version backward support.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:20Software paradoxes
- 9:29Physics and failure
- 13:07Software communities
- 24:06Erlang community
- 31:45Why Erlang matters
- 37:15Abstraction duality
- 42:32Process isolation
- 51:45Erlang features
- 59:56Q&A
related talks
49mAn Introduction to Erlang From behind the Trenches
45mElixir and the Internet of Things
53mIdioms for Building Distributed Fault-tolerant Applications with Elixir
41mIdioms for building fault-tolerant applications with Elixir
42mIt's about (run)time -- Elixir beyond the hype
03h 19mWorkshop - All Aboard The Elixir Express!
04mInterview
01h 06mWhat every Node.js developer needs to know about Elixir