Design Live Video Streaming - System Design | WinJob

System Boundary and Product Modes

Live video streaming at Twitch or YouTube scale is best described as three cooperating planes. The control plane owns sessions, stream keys, entitlements, moderation commands, and regional placement. The media plane owns ingest, transcoding, packaging, object storage, origin shielding, and CDN delivery. The analytics plane owns player telemetry, creator dashboards, ad measurement, and quality-of-experience aggregates. Naming those planes early keeps the answer from collapsing into a single overloaded service.

The first architectural fork is product mode. Interactive events such as esports commentary, auctions, and live shopping need low glass-to-glass latency, usually LL-HLS, WebRTC preview, or a hybrid path. Broadcast-heavy viewing can accept 4-8 seconds of latency if it buys better cache efficiency, fewer rebuffers, and lower egress cost. A senior answer states the operating mode first, then shows how policies switch by device, network score, entitlement tier, and content class.

The core scope is RTMP/SRT ingest, session control, ABR ladder generation, HLS/DASH packaging, tokenized playback, CDN fan-out, live chat sidecar, DVR rewind, stream health telemetry, DRM for premium content, and fail-soft operations. Adjacent systems such as recommendation ranking, studio editing, or custom codec research are explicitly excluded unless the interviewer steers there. Anchor the rest of the design to measurable goals: p95 startup below 1.5 seconds in default mode, sub-2-second low-latency cohorts where supported, rebuffer ratio below 0.5%, publish availability at 99.99%, and in-region chat delivery below 300 ms.

javaOne Dark Pro

1 public final class IngestSession {
2   private final String streamId;
3   private final String region;
4   private final Instant leaseExpiresAt;
5  
6   public boolean isLeaseValid(Instant now) {
7     return now.isBefore(leaseExpiresAt);
8   }
9 }

pythonOne Dark Pro

1 def estimate_ingress_mbps(width: int, height: int, fps: int, bits_per_pixel: float = 0.08) -> float:
2     return width * height * fps * bits_per_pixel / 1_000_000

typescriptOne Dark Pro

1 export interface IngestLease {
2   streamId: string;
3   region: string;
4   expiresAt: string;
5 }
6  
7 export function isLeaseActive(lease: IngestLease, nowMs: number): boolean {
8   return Date.parse(lease.expiresAt) > nowMs;
9 }

Why interviewers care

Live Video Streaming interviews reward crisp scope, explicit trade-offs, and failure stories—not generic microservice diagrams.

The failure that defines the design

The outage to narrate is the rebuffering storm during a peak live event. A popular stream spikes to millions of concurrent viewers, a CDN edge or a transcode tier saturates, and players across a region start rebuffering at once — the dreaded spinning wheel during the big moment. The fix is structural: a deep ABR ladder so players drop to a lower bitrate instead of stalling, aggressive CDN edge caching so the origin is shielded, and graceful degradation that sheds the top rendition fleet-wide before it drops anyone. A streaming platform is judged on rebuffer ratio under peak concurrency, not on whether the stream plays for one viewer.

Key Highlights

•Split control, media, and analytics planes before drawing boxes.
•Declare product mode (interactive vs broadcast latency) up front.
•State explicit SLO numbers interviewers can challenge.

1	public final class IngestSession {
2	private final String streamId;
3	private final String region;
4	private final Instant leaseExpiresAt;
5
6	public boolean isLeaseValid(Instant now) {
7	return now.isBefore(leaseExpiresAt);
8	}
9	}

1	def estimate_ingress_mbps(width: int, height: int, fps: int, bits_per_pixel: float = 0.08) -> float:
2	return width * height * fps * bits_per_pixel / 1_000_000

1	export interface IngestLease {
2	streamId: string;
3	region: string;
4	expiresAt: string;
5	}
6
7	export function isLeaseActive(lease: IngestLease, nowMs: number): boolean {
8	return Date.parse(lease.expiresAt) > nowMs;
9	}

System Boundary and Product Modes

Why interviewers care

The failure that defines the design

Key Highlights

Section Rescue Kit