Design a Notification System

hard
queues
fan-out
retries
dedup

Problem brief

A notification system takes a request like "tell these users their order shipped" or "tell all 10 million users about the sale" and turns it into push notifications, text messages and emails, through third-party providers that are slow, rate-limited and occasionally down. Sending one message is trivial. The hard parts are respecting each user's preferences, fanning a single broadcast out to millions of devices in minutes, retrying failures without hammering providers, and making sure a retry never sends the same notification to the same person twice.

Practice workspace

Guided practice or a locally saved 45-minute mock.

Step 1 of 12

Functional Requirements

What does the notification system need to do, and what would you explicitly leave out of version one?

Reference solution hidden

Try answering in the workspace above first. Reveal the full worked solution — data model, architecture, and trade-offs — whenever you want to compare.

Open the full solution page →