Real-Time Sync

Discovery

Infer from context, then confirm:

1. Direction? — Server → client only (feed, notifications, live count), or bidirectional (chat, collaborative editing, presence)?
2. Transport constraint? — Serverless/edge (no persistent connections), self-hosted (full control), or behind a load balancer?
3. Existing infrastructure? — Redis available? Is the backend stateless across multiple instances?
4. Failure tolerance? — Can the user miss events during a disconnect, or must all events be delivered?

Transport Decision

Pick once. Switching later is expensive.