Why I choose Phoenix
summary
Chooses Elixir and Phoenix for concrete wins: lightweight millions of 1KB processes that isolate crashes and simplify parallelism; raw HTTP requests often measured in nanoseconds on a Heroku dyno; built-in tooling like mix test with doctests and coverage; observability via Phoenix Dashboard/Telemetry; generators plus Phoenix gen auth for authentication; first-class channels and LiveView for websocket-driven UIs; Livebook for runnable, shareable docs tied to a running app; real apps (React Native frontend, energy-grid dashboards) handle big traffic spikes without CPU or memory blips.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:54Moving from Ruby to Phoenix
- 4:57Parallelism in Phoenix
- 9:51Reason two: Phoenix is incredibly fast
- 11:37Phoenix testing
- 16:12Dashboard metrics
- 17:58Separation of concerns
- 19:46Rails-like generators
- 20:08Built-in authentication
- 21:32Channels and WebSockets
- 23:38LiveView for real-time
- 26:49LiveBook for docs
- 30:38Q&A
related talks
01h 00mPhoenix a Web Framework for the New Web
45mPhoenix a web framework for the new web
41mElixir & Phoenix – fast, concurrent and explicit
44mElixir & Phoenix - Fast, Concurrent and Explicit
40mTaking Off with Phoenix
50mPhoenix Framework: a (Truly) Fullstack Stack for Building Real-Time Web
01h 00mPhoenix: an Intro to Elixir's Web Framework
44mRise of The Phoenix - Building an Elixir Web Framework
