RETURN TO SYSTEM DESIGN VAULT (55)BLUEPRINT #18 // Medium
#18MediumCore Distributed Systems

Design Google Calendar

ASKED IN INTERVIEWS AT:GoogleLinkedIn

EXECUTIVE SUMMARY & PROBLEM STATEMENT

Design an enterprise calendar scheduling platform supporting recurring events, timezone transformations, meeting conflict detection, and real-time reminders.

SCALE ESTIMATION & TRAFFIC ENVELOPE

DAILY ACTIVE USERS / TPS200 Million DAU
READ / WRITE TRAFFIC RATIO10:1 Read-to-write
5-YEAR STORAGE CAPACITY1 Billion events/year = ~500 GB metadata annually

FUNCTIONAL REQUIREMENTS

  • [1]Create single and recurring calendar events (RRULE)
  • [2]Invite attendees and check mutual availability
  • [3]Send reminder notifications

NON-FUNCTIONAL REQUIREMENTS

  • •Zero double-booking on confirmed bookings
  • •Instant conflict detection across timezones
  • •Offline sync support on mobile

CORE ARCHITECTURAL COMPONENTS

Calendar API Gateway
Recurrence Expander Engine
Interval Tree Availability Service
Timezone Converter
Delayed RabbitMQ/Kafka Reminder Service

DATA SCHEMA & PERSISTENCE

Events (event_id, creator_id, title, start_utc, end_utc, rrule), AttendeeEvents (user_id, event_id, status)

DISTRIBUTED TRADE-OFFS & FAILURE MODES

  • ⟡Pre-expanding recurring events into database rows vs expanding RRULE string on-the-fly during calendar month views.