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.

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

How the design evolves

Stage 1: Single Server and Database

See why sending to every subscriber from the web server does not scale.

What was missing: Sending an issue should not run inside the web server.

Why that's risky: Sending a million emails ties up the same process that serves readers, so the site slows down on every send.

What gets added: One server that saves signups, shows archive pages and sends each issue to every subscriber itself.

Trade-offs: Simple, but sending and serving fight each other.

Stage 2: Separate Reads and Signups, Add a Cache

Split the paths and serve archive pages from memory.

What was missing: Reads and signups share one path.

Why that's risky: A new issue can take a moment to appear in the cache.

What gets added: An archive service reading from a cache, a subscribe service that stores each signup under a unique email per newsletter, and one database.

Trade-offs: Reads are fast but slightly stale; signups are idempotent so a double click does nothing.

Stage 3: CDN for the Archive

Serve archive pages from the edge.

What was missing: Every archive read reaches our servers.

Why that's risky: A new issue needs its edge copy purged or readers see the old archive page.

What gets added: A CDN in front of the archive.

Trade-offs: A short TTL or purge on publish keeps the archive fresh.

Stage 4: Fan-Out Sending and Limits

Send each issue to subscribers in batches through a queue.

What was missing: Sending blocks the web servers and bots can fill the list with fake addresses.

Why that's risky: If workers fall behind, a send that should take an hour takes much longer.

What gets added: A send queue that carries confirmation emails for new signups and one batch of subscribers per new issue, workers that send each message and record delivery, a signup rate limiter and monitoring.

Trade-offs: Email providers throttle senders and judge reputation, so workers send at a steady rate and stop sending to addresses that bounce; sending faster risks landing in spam.

PRISM
System Design Interview
Round 1 of 4 · Architecture Design · 60:00 remaining
PRISM logo PRISM logo
Problems
AI Interview
Interview Challenges
Build & Stress Test NEW
System Architectures
Design & Fix NEW
Interactive Roadmap
Problems
Today's mission
Notifications
    Theme
    Pricing Community NEW Send feedback Report a problem NEW
    Sign in
    Theme
    Community NEW Send feedback Report a problem NEW
    All problems
    Phase
    Build & Stress Test
    Phase 01: Thinking in Systems
    Upcoming

    Components

    User
    CDN
    Load Balancer
    Server
    Cache
    Database
    Blob Storage
    Search Index
    Queue
    Worker
    Rate Limiter
    Service
    API Gateway
    Reverse Proxy
    WebSocket Server
    Third-party API

    Inspector

    Notes
    Use clear names so your design intent is easy to understand.
    Good
    Name by business meaning
    "Order API", "Restaurant Service"
    Avoid
    Generic names = zero signal
    "Server 1", "API", "Queue"
    A short description for each component makes feedback much better.
    100%
    Start by identifying:
    • Users & entry points
    • APIs & services
    • Databases & storage
    • Traffic flow & scale

    Round 1 of 4 Architecture Design

    Run a simulation to see results.

    Time Remaining
    60:00
    System Design Interview

    What are the core functional requirements?
    What are the key non-functional constraints?

    Questions

    Start Evaluation to unlock questions.

    Test yourself like it's the real thing.

    Interview prep guide
    Architecture Design
    Draw your system on the canvas. Define components, connections, and data flow.
    FR & NFR Requirements
    Answer functional and non-functional requirement questions about your design.
    MCQ Round
    Multiple choice questions testing your depth on the chosen system.
    Tradeoff Analysis
    Justify your design decisions and defend your architectural tradeoffs.
    AI interviews left 0left
    This week 0 / 0
    Used today 0 / 0

    Choose a Problem
    No problem selected
    • 30 min
    • 45 min
    • 60 min
    Round 2 of 4
    MCQ Round
    Answer multiple-choice questions based on your design.

    Exit Interview?

    You're in the middle of an interview session. Leaving now will end your current attempt.

    Your progress will be saved.

    Open a saved design

    Select a design to load into the canvas.

    My Evaluations

    Your past evaluation sessions

    Here’s a simple request flow that follows the expected layer order.

    External User
    →
    Edge CDN → API Gateway → Load Balancer
    →
    Compute App Servers / Services
    →
    DataAccess Cache
    →
    Storage Database / Search Index
    →
    Async Queue → Worker

    Tip: keep arrows moving forward through layers (Edge → Compute → Storage). Avoid sending storage back to compute.

    Evaluation Instructions

    Read the rules carefully before starting. The test auto-submits on refresh.

    Before you start

    • Build your architecture on the canvas. The timer starts when you click Start Evaluation.
    • Don't forget to answer Functional Requirement and Non Functional Requirements.
    • When satisfied with your design, click Next to lock it and view the questions.
    • Please answer final step questions to complete the evaluation.

    Dos

    • Do read each question carefully before answering.
    • Do include required components to maximize component coverage.
    • Do save a copy of your design if you want to keep it before submission.

    Don'ts

    • Don't refresh or close the tab during an active evaluation — this will auto-submit your answers.
    • Don't switch app modes or open another tab while the evaluation is running.
    • Don't attempt to edit the design after clicking Next; the workspace will be locked.

    All the best!!

    Confirm

    Input

    Notice

    Evaluation Report
    Report a problem

    Evaluation Complete

    Generating Your Report

    Hang tight — our AI is evaluating your design…

    Did you know?

    Loading…

    Share feedback

    Tell us what worked well and what we can improve.

    Let's personalize this

    Answer a couple of quick questions so we can tailor your journey and missions.

    Your welcome gift: of Full PRISM Access

    Your Pro access starts as soon as you press Start my journey.

    SYSTEM BRIEF

    System Constraints

    What the system must do — every item is a user-facing behaviour your architecture must support.

      ↑ Engineering Constraints

      These are the failure modes you must design against — latency SLAs, durability targets, traffic ceilings.

        ⇆ Architecture Constraints

        Core Concepts to Master

        Your Journey
        PHASE – –
        0 / 0 0%
        0
        Mock Interview Checklist

        Pick a topic to start

        Explore concept overviews, real-system examples, key tradeoffs, and interview talking points for each roadmap section.

        Phase Mastered

        You've conquered this phase. These are the skills you now own:

          +500 XP

          Company Interview Paths

          Progress Summary