Keynote: The Pendulum
summary
Argues that Elixir and Phoenix reattach stateful conversations to web apps while keeping the scalablity of request/response systems, claiming 10x faster than Rails on simple benchmarks and showing Phoenix performance pulls away as cores increase. Describes using lightweight isolated processes, supervision trees, a modified MVC that makes models and views pure functions with controllers handling impure effects, and notes the built systems (Phoenix servers, connection pooling and isolation) actually deliver repeatable fast results.
AI-written summary · about
chapters (17)
- 0:00Communicating excitement
- 1:00Roots of the pendulum
- 1:55Defining the pendulum
- 2:27The batch era of computing
- 6:19The move to interactive
- 9:12Graphical user interfaces
- 12:11Challenges in C programming
- 14:26Client-server architecture
- 16:01The rise of Microsoft
- 19:39Solving DLL hell
- 22:11The internet revolution
- 23:26Making the web stateful
- 26:57Java and scaling
- 30:28Pushing for interaction
- 32:12Revisiting stateful models
- 35:53Phoenix performance
- 37:39Future pendulum swings
related talks
30mPhoenix Is Not Your Application
47mGood behaviour: Cultivating Healthy Elixir Teams & Codebases
01h 16mKeynote 3: The Zen of Programming
55mKeynote: Exoskeletons, not Autopilots
45mKeynote: One Monolith, Many Teams: Growing an Org...
01h 01mArchitecture Decisions: A Case Study -
53mKeynote: Value Driven Development - Maximum Impact, Maximum Speed
19mKeynote – Adam Hooper