HLDArena
HLD-226·Caching & Consistency
Medium · 1,000 pts

Enterprise Calendar Scheduling, Recurrence & Sync

Design Google Calendar’s core event storage, RRULE recurrence expansion, and attendee calendar synchronization handling top-of-hour reminder bursts.

Max p99
≤ 55 ms
Availability
≥ 99.5%
Budget
≤ $5,550

Functional Requirements

  • FR-1POST /calendars/{user_id}/events — Creates single or recurring meetings and fans out attendee invites.
  • FR-2GET /calendars/{user_id}/agenda — Fetches expanded daily/weekly event view with read-after-write consistency.
  • FR-3PATCH & DELETE /calendars/{user_id}/events/{event_id} — Reschedules or cancels meetings and immediately invalidates attendee agenda caches.
  • FR-4Must absorb xx:00/xx:30 meeting-join storms and survive primary DB failover.

Workload Profile

Workday Baseline30,000 Agenda Read RPS / 4,200 Event Write RPS
Top-of-Hour Meeting Rush88,000 Read RPS / 11,000 Write RPS
Active Working Set24 GB active 30-day enterprise agendas
Traffic DistributionSynchronized spikes at :00 and :30 across timezones

Consistency Model

Read-after-write consistency on organizer/attendee agenda views so rescheduled links appear immediately.

Relevant practice for

Click an item in Inventory above, or press B to add a component, double-click to name, C to connect.

Design Write-up

Write under ### Architecture for Diagram to take that up directly

Compulsory section · if not written yet, Diagram reads from the start of your write-up.
Architecture: required·FRs mentioned: 0/4·0 boxes · 0 edges
0 words
Hidden Cases #4–#7 run automatically on Submit
Case 1: Smoke & API ContractInput Workload
Read RPS
2,000 rps
Write RPS
400 rps
Key Distribution
Uniform (Low Skew)
Chaos Fault
None (Healthy Cluster)
Expected Pass CriteriaASSERTIONS
• Tail Latency: p99 ≤ 110 ms
• Availability: ≥ 99.5%
Valid end-to-end Client → Compute → Storage topology