Elixir & Phoenix – fast, concurrent and explicit
summary
Elixir runs on the Erlang VM and Phoenix demonstrates extreme concurrency: benchmarks show 2 million WebSocket connections on one server and the BEAM supports processes up to ~268 million, each GC'd independently. Phoenix uses OTP supervisors with the “let it crash” restart model, channels for WebSockets, and Ecto’s explicit change sets and repo.insert for DB side effects. Functional features highlighted: immutable data, pattern matching, the pipe operator, compile-time macros, and explicit preloading to avoid N+1 queries.
AI-written summary · about
chapters (12)
- 0:00Introduction to Elixir Phoenix
- 3:32Why Elixir and Phoenix excel
- 7:04Testing and documentation benefits
- 10:21Pattern matching in Elixir
- 13:56Functional programming perspective
- 16:47Immutable data structures
- 22:06Actor model and concurrency
- 25:57Phoenix framework overview
- 29:52Change sets and validations
- 33:22Phoenix tooling and conventions
- 37:01When to choose Phoenix
- 40:31Closing and Q&A
related talks
44mElixir & Phoenix - Fast, Concurrent and Explicit
19mElixir – what it is and why is it amazing?
45mPhoenix a web framework for the new web
01h 00mPhoenix a Web Framework for the New Web
32mWhy I choose Phoenix
53mElixir: a potion to mix complexity and concurrency in real‑time
37mElixir - functional, concurrent, distributed programming
45mElixir: une potion pour mixer complexité et concurrence en temps réel