Practice: Design a Newsletter Platform
Newsletter platform inspired by Substack and Beehiiv: readers subscribe, issue archive pages are served from the edge, and sending an issue fans out through a queue to every subscriber.
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
- Let a reader subscribe (and unsubscribe) to a newsletter, with a confirmation email to avoid fake signups
- Show a published issue from the archive on a fast, shareable page
- Send a new issue to every subscriber through a queue and send workers, never from the web request
- Never send the same issue to the same subscriber twice, even when a worker retries
- Record which issues were delivered, and bounces and unsubscribes, for each subscriber
- Limit signups per IP so bots cannot fill a list or use the platform to spam addresses
Non-functional requirements
- Subscribe accepted < 100ms p99; archive page < 100ms p99 through the CDN
- Sending an issue to 1M subscribers finishes within an hour (about 280 emails per second sustained)
- No subscriber receives the same issue twice; each send is idempotent per (issue, subscriber)
- Handle 10K requests per second at peak, with about 90% archive reads and 1K signups per second during a promotion
- A send-worker crash resumes where it stopped instead of restarting the whole send
- 99.99% durability for subscriber lists
- 99.9% availability for subscribe and archive pages