What is the Phoenix Framework's approach to real-time communication with channels?

Phoenix Channels (Elixir) represent the state-of-the-art in real-time WebSocket architecture. Built on the BEAM virtual machine, Phoenix leverages Erlang's battle-tested concurrency model where each channel subscription runs as a separate lightweight process (1–2KB overhead). The architecture: (1) Channel modules — each topic (e.g., room:lobby) maps to a channel module with join/3, handle_in/3, and handle_out/3 callbacks; (2) PubSub — the built-in Phoenix.PubSub broadcasts across all nodes in a cluster via Erlang's distributed messaging (no Redis needed for Elixir clusters); (3) Presence — Phoenix.Presence uses CRDTs to track online users across cluster nodes with automatic conflict resolution; (4) Scale — the 2 million concurrent WebSocket connections on a single server benchmark (Gary Rennie, 2015) used Phoenix Channels. This was possible because BEAM processes are far lighter than OS threads. Phoenix's approach demonstrates that language/runtime choice is often more impactful than application architecture for WebSocket scalability.