Phoenix LiveView
Phoenix LiveView maintains persistent WebSocket connections between your server and every connected browser. That architectural choice delivers incredible user experiences but demands a platform that respects long-lived connections and in-memory state. Most platforms limit concurrent connections, restart containers daily, or charge extra for WebSocket support. Gigalixir was built for Elixir applications like LiveView from the start. We don't limit connections. We don't restart your containers arbitrarily. We configure clustering so PubSub broadcasts reach every connected client across every node.
No Connection Limits: LiveView applications can have thousands of simultaneous WebSocket connections. We don't throttle, limit, or charge extra for concurrent connections. Phoenix can handle over two million connections per node. We don't get in the way.
No Arbitrary Restarts: LiveView state lives in server processes. When a container restarts, every connected user loses their session state. Other platforms restart containers for maintenance, scaling, or just because. We don't restart your replicas unless something is actually wrong.
Native Distributed PubSub: When you cluster your nodes with libcluster, Phoenix PubSub broadcasts work across your entire cluster automatically. Push an update and every connected client receives it, regardless of which node they're connected to. No Redis. No external message broker.
Uploads and Long Operations Just Work: LiveView's file uploads stream through persistent connections. Large file uploads that take minutes don't get interrupted by platform timeouts. Background operations that update the UI in real-time have the stability to complete.