The Adaptive Stream

The incident

The lecture videos were fixed 1080p files. On the commute — the exact moment students watched — every tunnel and every weak cell killed playback dead. Support tickets said 'the video is broken.' The video was fine. The delivery model was from 2009.

Why the obvious approach fails

Serving a single video file makes bitrate a decision the server takes once and the network gets no vote on. Real connections fluctuate constantly, and a fixed-bitrate stream has exactly two states: playing and stalled. The player can't step down to survive a dip, because there's nothing to step down to. Adaptive streaming inverts this: the video exists in several qualities, cut into seconds-long segments, and the player chooses each next segment based on the bandwidth it's actually seeing. Quality becomes elastic; playback becomes continuous. Users forgive a soft picture. They don't forgive a spinner.

The standard

• +Video ships as HLS (or DASH): 2–6 second segments in 4–5 quality variants, from low-bandwidth to full HD.
• +The master manifest lets the player switch quality mid-stream, per segment, with no rebuffer on downshift.
• +Audio continuity is protected first — on severe dips, picture degrades before sound stutters.
• +Segments are CDN-delivered; origin serves manifests and misses, never the hot path.
• +Playback health is measured: rebuffer ratio and average bitrate per network tier are tracked per release.

Composes with