Handling Large Blobs hard
How does HLS/DASH handle a user moving from WiFi to 4G (Variable Bandwidth)?
- A It pauses the video.
- B It lowers the volume.
- C It uses UDP.
- D The client downloads a Manifest file listing chunks in multiple quality levels (1080p, 720p, 360p). The player automatically requests the next chunk from the highest quality level that fits the current bandwidth.
Answer: D. The client downloads a Manifest file listing chunks in multiple quality levels (1080p, 720p, 360p). The player automatically requests the next chunk from the highest quality level that fits the current bandwidth.
The logic is largely client-side (Pull-based). The server just serves static chunks.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- Why do modern sites serve images in WebP or AVIF format?
- What does the acronym BLOB stand for?
- Why do we sometimes convert binary images to Base64 strings?
- What is an 'Origin Shield' or 'Mid-Tier Cache' in a CDN architecture?
- For a feed with 100 images, why use 'Lazy Loading'?
- To avoid overloading the Application Server with bandwidth, how should a client upload a 10GB file?