Problem Understanding
Restate the problem in your own words.
Design Cricbuzz (Live Sports Score Broadcast)
Design a live cricket-score broadcasting system: a single in-venue operator records each ball as it happens, and the system delivers that update to tens of millions of concurrent viewers globally in under two seconds, with ball-by-ball commentary, scorecards, and push notifications on key events. The architecture is dominated by the fan-out side — connection-tier sizing, edge caching for cold readers, and the push storms triggered by wickets — not by the trickle of writes coming from the venue. The decisive trade-off is the WebSocket / SSE push tier vs. a short-TTL CDN snapshot, with most production systems running both in parallel.
- CricbuzzCricket-first; ~50 M MAU; a finals match peaks at tens of millions concurrent.
- ESPN / ESPNcricinfoThe original cricket-score site; richer match-history corpus, similar live tier.
- FlashScore / SofaScoreMulti-sport live scores; same 'one match, many viewers' fan-out, scaled across thousands of matches.
- Yahoo Sports / NFL Game CenterAmerican-sports analogue; the live-event surface in Yahoo / NFL apps.
Your task: read the problem above, then write what the system is, who uses it, the rough scale, and the headline UX expectation — in your own words. Submit for AI review when you're ready.
Click any step in the sidebar to jump around — sections don't have to be done in order. Press ? any time to see all shortcuts.