Anatomy of a Real Time Elixir App
summary
Dives into Phoenix source to show exactly how sockets become routes (each socket compiles into dispatch functions), how Cowboy’s WebSocket and Phoenix’s transport call the app’s connect/3 → connect/1 flow, and how joining starts a supervised GenServer so channel = pid while the topic is a map key. Demonstrates PubSub subscription per channel, JSON serialization via the Cowboy handler, and that messages are handled serially (so channels can become bottlenecks).
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:54What is real time
- 3:41Why anatomy
- 7:23Phoenix Channels
- 11:18WebSockets
- 12:40Socket Macro
- 15:31Socket Paths
- 18:23WebSocket
- 21:18Connect
- 23:07WebSocket Handle
- 27:25Handling Info
- 30:12Reply
related talks
01h 00mPhoenix: an Intro to Elixir's Web Framework
46mBuilding a Realtime Websocket API in Phoenix
41mElixir & Phoenix – fast, concurrent and explicit
44mElixir & Phoenix - Fast, Concurrent and Explicit
37mKeynote: All Aboard The Stateful Train
03h 19mWorkshop - All Aboard The Elixir Express!
44mRise of The Phoenix - Building an Elixir Web Framework
39m"Elixir-based Ruby Web Server"