ScaleCrafts

Design Twitch

HardLive videoTranscodingChat

Let creators stream live video to millions of viewers with low delay and live chat, like Twitch.

Functional requirements

  • Streamers broadcast live from their PC
  • Viewers watch with selectable quality
  • Live chat alongside each stream

Non-functional requirements

  • Under 5 seconds from camera to viewer
  • Popular streams scale to millions of viewers
  • Chat messages arrive in under a second

Scale

  • 100K concurrent live streams
  • 10M concurrent viewers
  • The top 1% of streams draw most viewers

How you’ll be scored

10 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works

What interviewers look for

  • Clarify before you draw. State what is in and out of scope. For “Design Twitch”, that starts with: Streamers broadcast live from their PC; Viewers watch with selectable quality; Live chat alongside each stream. Interviewers notice candidates who pin the requirements down first.
  • Turn the scale into numbers. The scale (100K concurrent live streams; 10M concurrent viewers; The top 1% of streams draw most viewers) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
  • Show how each quality is met. Your design should visibly deliver: Under 5 seconds from camera to viewer; Popular streams scale to millions of viewers; Chat messages arrive in under a second. Saying that it does isn’t enough; point to the part of the design that makes it true.
  • Expect follow-ups on the hard parts. Interviewers usually probe live video, transcoding and chat here. This is a hard problem, so interviewers expect depth: what breaks first at this scale, how each failure is contained, and which trade-offs you accepted on purpose.
  • Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.

Related problems

Loading your workspace…