Grokking the System Design Interview, Volume II
0% completed
Reminder Alert System: Data Model and Storage
Step 5: Data Model and Storage Design
With the high-level design drawn, we turn to the data itself. The schema has to serve two read patterns well, and everything else in this step follows from them.
- Look up reminders by next execution time. The Scheduler asks "what is due now?"
- Look up reminders by user. The app lists a user's reminders, and the system computes their next occurrences.
No single key serves both patterns, so we denormalize: we store each reminder in two tables, each keyed for one pattern
.....
.....
.....
Like the course? Get enrolled and start learning!
Reading Progress
0%