Practice: Design a To-Do Sync App
To-do app inspired by Todoist and Google Tasks: lists sync across a person's devices using sync tokens, reads come from a cache, and pushes and reminders are sent in the background.
Build this system yourself on the canvas below. Add components, connect them, and run traffic simulations to see where your design holds up and where it breaks.
Functional requirements
- Show a person's lists and tasks, and let them add, edit, reorder and complete tasks
- Sync every change to all of the person's devices using a sync token, so a device only fetches what changed since it last synced
- Work offline: changes made without a connection are queued on the device and merged when it reconnects
- Resolve a conflict when two devices change the same task (for example last write wins per field)
- Send a reminder at the due time to the person's devices
- Limit how often one client can sync, so a buggy app cannot hammer the service
Non-functional requirements
- Sync request < 100ms p99 when nothing changed, served from the task cache
- A change made on one device shows on the others within 5 seconds
- Handle 4K sync requests per second at peak, with about 800 task changes per second
- No saved task is ever lost (99.99% durability); a sync that fails halfway can be retried safely
- Reminders are sent within 1 minute of their due time, and exactly once per task
- Scale to 10M users, with each person's tasks living together for cheap sync queries
- 99.9% availability; the app keeps working offline when the service is down