ORIGINAL COMPANY-CONTEXT PRACTICE
Recover video playback when a content edge fails
Original practice scenario: A hypothetical streaming player requests sequential video segments from a nearby edge that becomes slow. Design fallback while preserving smooth playback and bounded origin load.
Written for independent practice using company context; this is not a verified question from a company interview.
A REASONED APPROACH
Model answer.
Use the player buffer and observed segment delivery as decision signals. A fallback strategy should protect playback while avoiding synchronized retries that overwhelm another edge or the origin.
Work through it
- Track buffer duration, segment identity and delivery deadlines, distinguishing a missing segment from a transiently slow request and a failed authorization.
- Retry idempotent segment requests with bounded concurrency, selecting a compatible alternative location or lower bitrate under an explicit adaptation policy.
- Add jitter, circuit-breaking and origin protection, then test edge failure during seeks, network switches and live content with short availability windows.
Tradeoffs to discuss
- Aggressive fallback reduces stall risk but can waste bandwidth through duplicate downloads; longer waits preserve bandwidth while consuming buffer.
Common pitfalls
- Do not switch to a representation whose segment timeline is incompatible with the current playback position.
- A successful HTTP response must still be validated as the expected authorized media segment.