Real Decision
Why realtime communication was extracted from the rest of the platform.
Problem
WebSocket workloads have different connection patterns, scaling needs and failure modes than standard APIs, especially when multiple clients and operational systems rely on live updates.
Decision
Realtime delivery was isolated into a dedicated WebSocket service so connection management, event fan-out and scaling policies could be optimized without affecting the rest of the platform.
Why Not
Run realtime communication inside every application service.
Treat persistent connections as a normal extension of synchronous APIs.