Comparison and Commentary on "Application Operating System"
summary
Argues that Erlang/BEAM is less about magic and more about tradeoffs: Erlang uses hundreds of thousands of lightweight fiber-like processes to mitigate functional immutability, provide supervisor trees for robust recovery, and enable hot code swapping and distributed session proxies. Compares concrete tools—OTP, ports, SSHD, systemd and native C/C++—and shows a practical BBS design mixing Erlang for messaging/session proxying with OS processes for external “doors” and SSH authentication; the hybrid approach works and exposes clear runtime and security trade-offs.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 3:22Alert Logic
- 4:01Narrative
- 6:49Layers
- 10:16Virtualization
- 11:24Overhead
- 12:01Models
- 12:41Nodes
- 13:48Operating System vs Application Operating System
- 15:17Microservice Architecture
- 16:44Process Model
- 19:27Why Erlang Processes
- 22:34Does Erlang Processes Make Anything Faster
- 25:04Security Model
- 28:56Supervisor Logic
- 30:47Networking
- 32:05Resource Management
- 32:48Dynamic Code
- 34:27Thought Exercise
related talks
43mConcurrency Oriented Programming in a Modern World
51mThe Erlang VM or How I Started Loving Parallel Progamming
43mConcurrency Abstractions for Application Security
42mConcurrency Oriented Software
40mKeynote: Fireside Chat on code design
52mConcurrency Oriented Programming in a Modern World
49mBEAM Concurrency in Action
35mDiving into Erlang is a one-way ticket