Idioms for Building Fault-tolerant Applications with Elixir
summary
Elixir runs lightweight isolated processes that communicate by message passing and are supervised so crashing components are restarted automatically, demonstrated with supervision tree tooling and LiveDashboard/Observer. Phoenix and WhatsApp hit 2 million connections on a single node after fixing a 50k bottleneck by spotting overloaded process queues. Extensions shown include NX (GPU numerical work), Ecto/ecto SQL libs, Nerves for embedded, Hex packages, and a Pinterest case of 95% fewer servers saving ~$2M/year.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:49Trad Safety
- 4:47Functional Programming
- 8:26Airlink
- 11:00WhatsApp
- 14:19What is Elixir
- 15:15Process
- 17:13Crash
- 21:01Applications
- 28:04Message Passing
- 32:58Accessibility
- 38:00Productivity
related talks
41mIdioms for building fault-tolerant applications with Elixir
53mIdioms for Building Distributed Fault-tolerant Applications with Elixir
03h 19mWorkshop - All Aboard The Elixir Express!
44mElixir & Phoenix - Fast, Concurrent and Explicit
01h 06mWhat every Node.js developer needs to know about Elixir
53mElixir: a potion to mix complexity and concurrency in real‑time
41mElixir & Phoenix – fast, concurrent and explicit
19mElixir – what it is and why is it amazing?