Section 9: Sixteen Million Buzzes at :50 - Deep Dive: Reminders & the Top-of-the-Hour Burst

Executive Summary: Reminders are fired by the clock, not a person, and are violently bursty, with 16 million due in a single minute: :50 or :20, ten minutes before the hour and half-hour. A Horizon Builder pre-stages the next 48 hours (200 GB) into minute buckets, and a Timer Service leases each bucket a minute early, fires at the tick with fencing tokens, and version-checks entries against local tombstones so edited or cancelled meetings never buzz. The burst lands on a push gateway provisioned for ~600K/s, never on the database.

Platform Sync is now on every calendar. The interviewer picks the next thread: "Monday, 08:50 in New York, 13:50 UTC. How many phones buzz, and what makes them buzz on time?"

Why Reminders Are a Different Workload

Everything so far was triggered by a person. A reminder is triggered by the clock, and that turns the system's shape inside out:

• Write-once, fire-later. The ledger's ~1B reminders a day average ~11.6K/s, but here the average is misleading.
• The burst is structural. The peak hour carries 8% of the day (80M), and 40% of that lands on the :50 and :20 minutes, so ~16M are due in a single minute. That isn't a traffic accident. It's how people book meetings.
• The target moves. Between scheduling and firing, an event can be edited, moved, cancelled or declined.

"The good news: every one of those 16 million is known minutes to days ahead. A burst you can see coming is a scheduling problem, not a scaling emergency."