YouTube data platform — Requirements

I start with 1B daily viewers, 5 playback sessions per viewer, 600 watched seconds per session, a 15-second heartbeat, 100 other events per viewer, and a 3× peak. That produces 300 events per viewer, 300B events per day, 3.47M events/s average, and 10.42M events/s peak. The weighted 767-byte event gives 7.99 GB/s peak ingress. With stated benchmarks and 40% reserve, I provision 584 regional collectors, about 280 heartbeat partitions, 279 Flink tasks, 112 batch executors for the four-hour window, 4.83 PB of seven-day Kafka capacity at RF3 before broker adjustments, and 46 TB of compressed Bronze growth per day. I verify stream state, checkpoints, lake layers, serving QPS, and scan volume separately, then replace assumptions with load-test results.