When Is Liveview a Good Fit
summary
LiveView requires Elixir on the backend and Phoenix; it shines for IO‑bound web UIs where the server keeps state and pushes tiny diffs over websockets, avoiding extra APIs or services. The BEAM starts millions of processes cheaply and Phoenix handles millions of sockets (benchmarked up to ~2M per server), so LiveView favors low P95 tail latency and realtime features. It is a poor choice for CPU‑bound work like video transcoding, has thinner IDE tooling, and Cars.com runs it at scale but warns above 25 million active users.
AI-written summary · about
chapters (7)
- 0:00Introduction to LiveView
- 1:11What is Elixir and when it fits
- 10:10Runtime characteristics of Elixir
- 15:10When Elixir is a good fit
- 25:30What is LiveView
- 30:22When LiveView is a good fit
- 41:21Q&A and common issues
related talks
39mBeyond Liveview: Real Time Features With Liveview
44mElixir & Phoenix - Fast, Concurrent and Explicit
24mLiveView and Web Components
55mLiveViewJS is the anti-SPA library for reactive app development in NodeJS and Deno
44mWhat's new in LiveView
01h 00mPhoenix a Web Framework for the New Web
45mPhoenix a web framework for the new web
48mCoding LiveView