Elixir: Happy Developers and Scaleable Backends
summary
Claims that Elixir’s power comes from the BEAM processes model and OTP supervisors with a “let it crash” restart strategy, shows pattern matching and multiple function heads as real, usable language features, and demos using Phoenix Live View to ship interactive UIs server‑side. Concrete results include CodeSandbox running with about a million requests per hour backed by just two backend developers, plus an internal support portal built in Live View that cut manual support work and sped iteration.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:17Why developers love Elixir
- 2:44Reasons not to use Elixir
- 4:51Pattern matching in Elixir
- 8:08BEAM VM and OTP
- 10:15Let It Crash philosophy
- 13:50Concurrency in BEAM
- 14:34Phoenix and LiveView
- 16:41CodeSandbox scaling with Phoenix
- 17:24Internal portal with LiveView
- 18:49LiveView in React
- 21:39Summary
related talks
28mRuby + Elixir: Polyglotting FTW!
53mBuilding Performant Backends with Elixir
42mIntroduction to Elixir for Rubyists
39mElixir: Power of Erlang, Joy of Ruby
34mRubyists, have a sip of Elixir!
32mElixir for the rubyist
52mA Rubyist's Survival Guide to Elixir and Phoenix
51mFrom Ruby to Elixir: Developing Web Applications