Phoenix a web framework for the new web
summary
Phoenix claims real performance and real productivity by building on Elixir and the Erlang VM and actually demonstrates it: transport-agnostic channels and a PubSub let sockets scale to 2 million connections on one machine (OS socket limits stop higher) and a Wikipedia-sized broadcast reaches all clients in about three to four seconds. Concurrency uses tiny VM processes with per-process garbage collection, supervised trees and Observer to find bottlenecks; practical tooling includes generators, live reload, mix and Hex.pm and a Programming Phoenix book.
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:00What is Phoenix
- 3:50Phoenix Channels
- 7:44What makes Phoenix special
- 13:56What is Phoenix today
- 14:21The false dichotomy
- 16:00Benchmarks
- 16:52Performance results
- 20:37Process isolation
- 22:37Productivity overview
- 24:22Phoenix website
- 24:45Programming Phoenix
- 25:13MVC
- 25:33Generators
- 26:52Productivity
- 29:01Shortterm relativity
- 29:22Longterm productivity
- 31:27Phoenix inside view
- 35:04Applications
- 36:41Observer
- 44:00Summary
related talks
01h 00mPhoenix a Web Framework for the New Web
41mElixir & Phoenix – fast, concurrent and explicit
50mPhoenix Framework: a (Truly) Fullstack Stack for Building Real-Time Web
44mRise of The Phoenix - Building an Elixir Web Framework
44mElixir & Phoenix - Fast, Concurrent and Explicit
32mWhy I choose Phoenix
01h 00mPhoenix: an Intro to Elixir's Web Framework
40mTaking Off with Phoenix