The NeverEnding Application
summary
A playable Hanabi server uses Elixir processes and ETS for in‑memory shared state, a Phoenix websocket channel to push tiny move events, and an Elm front end that only redraws on full game updates. Moves are persisted with append‑only event storage and replay so hot code changes can rebuild state, and Distillery releases enable hot code reloading worked live on a DigitalOcean box with no Elixir installed. Tradeoffs: snapshotting, backpressure, and migration complexity.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:53Upgrade App Script
- 12:14Websockets
- 14:44Phoenix Socket Library
- 20:05Loading Games
- 26:44Upgrade a Release
- 28:48Application Architecture
related talks
37mKeynote: All Aboard The Stateful Train
45mElixir: une potion pour mixer complexité et concurrence en temps réel
53mElixir: a potion to mix complexity and concurrency in real‑time
44mElixir & Phoenix - Fast, Concurrent and Explicit
19mElixir – what it is and why is it amazing?
48mElixir by the Bellyful
41mElixir & Phoenix – fast, concurrent and explicit
44mIdioms for Building Fault-tolerant Applications with Elixir