[ EXECUTIVE TEARDOWN // TL;DR ]
In-memory broadcast only reaches the local process — multi-instance real-time needs a shared backplane (Redis pub/sub).
Scope subscriptions into rooms so each client receives only the streams it watches, collapsing bandwidth and CPU.
Coalesce high-frequency sources on the server to a renderable frame rate before broadcasting.
Handle backpressure at the source, not after it has already flooded the client.
A single WebSocket server streaming telemetry to a few clients is a weekend project. Feeding thousands across multiple instances is systems work. I learned that on streamerOS: the “one process holds every socket” sketch sailed on one pod and face-planted the moment we scaled out. Each instance owns its own connection table, so A cannot fan out to subscribers that landed on B; broadcasts die at the process boundary and your graphs freeze.
The horizontal-scaling problem
Once you run more than one server process behind a load balancer, connections fan out across instances.…