Real-Time and Streaming System Design Questions

Designing client-facing, always-on live delivery systems: real-time communication transports (WebSockets, server-sent events, long-polling, WebRTC, MQTT), connection lifecycle and scaling for millions of persistent connections, presence, pub/sub fan-out to online users, chat and notifications, live feeds and tickers, real-time collaboration (CRDT vs OT, offline sync and reconciliation), and live and on-demand video delivery (ingest, transcoding, adaptive bitrate, CDN delivery, low-latency protocols, playback entitlement and content protection). Covers latency budgets, per-client ordering, delivery guarantees across disconnect and reconnect, per-client backpressure, capacity estimation for connection fleets, authentication, authorization, and revocation for real-time channels and premium content, and operational readiness (SLOs and error budgets, observability and incident response, rate limiting, safe rollout, and load and chaos testing) for live-delivery platforms. Data-pipeline stream processing (Kafka or Flink jobs, windowed aggregation, exactly-once pipelines, real-time analytics ingestion) is out of scope.

MediumSystem Design
66 practiced

Design an offline-first synchronization architecture for a mobile client (for example a CRM app) that allows creating and editing records offline, supports conflict detection and resolution, and syncs efficiently across varying bandwidth, including partial syncs when bandwidth is limited. Describe data models, client change queues, batching thresholds, retry/backoff policies, the server-side reconciliation algorithm, and how you would present merges to users.

EasyTechnical
59 practiced

Explain eventual consistency in the context of real-time client updates. Describe the trade-offs between latency and strong consistency, examples of acceptable eventual consistency (social feeds) versus unacceptable cases (financial transfers), and how to design reconciliation processes and user-visible indicators for divergence.

EasyTechnical
44 practiced

You need to implement a live, high-fan-out feed (for example a live sports score or a real-time dashboard) that is mostly one-way, server-to-client, and must reach up to 100k concurrent clients with low latency. Between SSE and WebSockets, which would you choose and why? Consider scalability, proxies/CDNs, mobile clients, TLS, automatic reconnection behavior, and how you would implement efficient fan-out to many clients.

EasyTechnical
50 practiced

Describe a robust client-side feature detection and fallback strategy for environments where WebSocket is blocked or unreliable. Include how to detect failures/blocks (e.g., blocked Upgrade header, connection resets), how to choose between SSE and long-polling fallback, how to preserve session semantics and message ordering across fallback transitions, and how to keep server-side behavior consistent.

MediumTechnical
45 practiced

Draft a reconnection strategy for mobile clients connecting to a WebSocket real-time service that enforces server rate limits and must minimize battery usage. Include exponential backoff with jitter, maximum retry windows, progressive decay, fallback strategies to polling, and metrics to determine when to escalate or notify users.

Unlock Full Question Bank

Get access to all 14 Real-Time and Streaming System Design interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.