Lobbying with Elixir: Real-Time LiveView and OTP
summary
Demonstrates a working lobby system built with Elixir, Phoenix LiveView and OTP where each lobby runs as a per-lobby GenServer supervised and floated across a cluster, persisting to a datastore only as a checkpoint. LiveView syncs multiple browser windows in the demo and yields a drastic reduction in JS compared with a vanilla Phoenix channel client. Notes tradeoffs: Postgres/Redis notifications turn the DB into a bottleneck, LiveView uses Phoenix channel serialization and recommends keeping live views per page modest (under ~30, used 40+ in production).
AI-written summary · about
chapters (10)
- 0:00Introduction to game lobbies
- 1:51State and distributed systems
- 3:52Synchronization challenges
- 7:23Elixir and architectural design
- 9:33Live demonstration
- 12:02Vanilla JavaScript approach
- 16:02The LiveView alternative
- 19:40Comparison and benefits
- 22:12Conclusion
- 23:32Q&A session
related talks
37mMultiplayer games and (...) with LiveView
39mBeyond Liveview: Real Time Features With Liveview
40mThe Power & Performance of Phoenix LiveView
35mKeynote: Fireside Chat on LiveView, (...)
01h 13mKeynote: Phoenix LiveView - Interactive Apps without Javascript
35mBringing LiveView to the Client with Popcorn
30mTales of Using Phoenix LiveView at an Early Stage Startup
53mElixir: a potion to mix complexity and concurrency in real‑time