Uploaded October 2026 | Updated November 2026, 3 days ago
IPL final, the toss: crores of people open JioHotstar at the same time, and autoscaling won't save you.
System Design Interview, Day 002. The question: design it so it doesn't go down. Most candidates say "turn on autoscaling", and that's where the round slips away. Do the maths: ten lakh people open the app every minute before the toss, and a new server takes about three minutes to start. Thirty lakh people hit the old servers first.
- Fix 1: scale before the match. Forecast the peak from the last final and load tests, add a buffer, warm servers, databases and CDN capacity before the toss. Scale on concurrent viewers, not CPU
- Fix 2: the video pipeline. One stream from the stadium encoder, a transcoder makes qualities from 1080p down to 360p, a packager cuts six-second pieces at the same moments, one playlist per quality
- Fix 3: an origin shield. In live every piece is new, so every edge misses at once. A shield layer fetches each piece from your server only once
- Fix 4: adaptive bitrate. The phone measures its speed on every piece and steps quality down or up. The price: you watch a few seconds behind live
- The trap: video comes from the CDN, but login, the subscription check and the DRM licence still hit your servers at the toss. Cache the subscription check, spread token refreshes out
- Fix 5: a panic mode. A big wicket, millions press back. Feature flags switch off recommendations and watch history, circuit breakers skip slow services, the gateway sheds load. Video, login and payments keep working
- Fix 6: jitter for the ad break. Each phone waits a random half second to three seconds; retries use exponential backoff
What the interviewer wanted: more than autoscaling. Scale ahead, an origin shield, adaptive bitrate, a panic mode, and jitter.
Next System Design Interview episode: you send 500 rupees on UPI, the money leaves your account, but the app says failed. Where did it go? Comment: which moment is the hardest, the toss, the wicket, or the ad break?
kgptalkie.com
#shorts #SystemDesign #SystemDesignInterview #IPL #JioHotstar #LiveStreaming #CDN #Autoscaling #InterviewPrep #KGPTalkie
IPL final, the toss: crores of people open JioHotstar at the same time, and autoscaling won't save you.
System Design Interview, Day 002. The question: design it so it doesn't go down. Most candidates say "turn on autoscaling", and that's where the round slips away. Do the maths: ten lakh people open the app every minute before the toss, and a new server takes about three minutes to start. Thirty lakh people hit the old servers first.
- Fix 1: scale before the match. Forecast the peak from the last final and load tests, add a buffer, warm servers, databases and CDN capacity before the toss. Scale on concurrent viewers, not CPU
- Fix 2: the video pipeline. One stream from the stadium encoder, a transcoder makes qualities from 1080p down to 360p, a packager cuts six-second pieces at the same moments, one playlist per quality
- Fix 3: an origin shield. In live every piece is new, so every edge misses at once. A shield layer fetches each piece from your server only once
- Fix 4: adaptive bitrate. The phone measures its speed on every piece and steps quality down or up. The price: you watch a few seconds behind live
- The trap: video comes from the CDN, but login, the subscription check and the DRM licence still hit your servers at the toss. Cache the subscription check, spread token refreshes out
- Fix 5: a panic mode. A big wicket, millions press back. Feature flags switch off recommendations and watch history, circuit breakers skip slow services, the gateway sheds load. Video, login and payments keep working
- Fix 6: jitter for the ad break. Each phone waits a random half second to three seconds; retries use exponential backoff
What the interviewer wanted: more than autoscaling. Scale ahead, an origin shield, adaptive bitrate, a panic mode, and jitter.
Next System Design Interview episode: you send 500 rupees on UPI, the money leaves your account, but the app says failed. Where did it go? Comment: which moment is the hardest, the toss, the wicket, or the ad break?
kgptalkie.com
#shorts #SystemDesign #SystemDesignInterview #IPL #JioHotstar #LiveStreaming #CDN #Autoscaling #InterviewPrep #KGPTalkie










