BEAM There, Done That Concurrency, OTP, and the Evolution of the BEAM
19 snips
Feb 27, 2026 Andrea Leopardi, platform engineer and Elixir core team member with a decade in Elixir and OSS, discusses concurrency, OTP and the BEAM evolution. They explore telecom roots of concurrency, how Elixir abstracts OTP, differences between Erlang and Elixir learning curves, BEAM strengths like isolated processes and distribution, and advanced concurrency topics Andrea will teach.
AI Snips
Chapters
Transcript
Episode notes
Concurrency Originated To Detect Failures
- Concurrency in Erlang emerged from the need to detect failures by monitoring processes rather than to invent a language first.
- Francesco recounts telecom engineers replacing a human watcher with a second process to automatically restart failed components.
Human Supervisors Inspired Erlang Supervisors
- Early mobile telephony systems used a human watching logs to know when to restart a crashed system.
- Francesco tells how that human acted as a supervisor, inspiring automated monitors and supervisors in Erlang's design.
Start With Phoenix Then Learn OTP Internals
- Use Elixir's higher-level abstractions to reduce initial learning friction, then progressively learn OTP internals.
- Andrea and Francesco recommend becoming productive with Phoenix first, then study linking, monitoring and supervision to handle scale.