Design a Blog Platform

Blogging platform inspired by Medium and Ghost: authors publish posts, readers get pages from a cache and the CDN edge, and rendering and follower updates happen in the background.

Functional requirements

  • Show a post to a reader on a fast, shareable page, including images and the author's name
  • Let an author write, publish, edit and unpublish a post, with drafts saved before publishing
  • Render a post's page after it is published (or edited) in the background, so publishing returns quickly
  • Show a reader the latest posts of the authors they follow, newest first
  • Handle a post going viral: thousands of reads per second on one post must not slow the rest of the site
  • Limit how fast one account can publish or edit, so a bot cannot flood the platform

Non-functional requirements

  • Page response < 100ms p99 for published posts, served from the CDN and post cache
  • A published post or edit is visible to readers within 30 seconds
  • Handle 10K page requests per second at peak, with about 5 new or edited posts per second
  • A viral post can take 5K reads per second without reaching the database (cached at the edge)
  • 99.99% durability: a published post is never lost; scale to 10M posts
  • 99.99% availability for reading, even if publishing is down
  • Rendering workers can fall behind during a burst without losing a publish (queued, retried)

How the design evolves

Stage 1: Query the Database for Every Page

See why building a page from the database on every request does not scale.

What was missing: A post should not be rebuilt from the database for every reader.

Why that's risky: A viral post means thousands of identical page builds per second, all hitting the same database rows.

What gets added: One server that reads a post from the database and builds the page on every request, and saves new posts.

Trade-offs: Simple, and always shows the latest edit.

Stage 2: Post Service and Cache

Separate reading from publishing and serve posts from memory.

What was missing: Reading and publishing share one path and every page hits the database.

Why that's risky: After an edit the cache can show the old version until it is refreshed or invalidated.

What gets added: A post service reading from a cache keyed by post id, a separate publish service that writes to the post database.

Trade-offs: Readers may see a post a few seconds old, which is fine for articles.

Stage 3: CDN at the Edge

Serve popular posts from the edge so a viral post never reaches our servers.

What was missing: Every read still reaches our servers, and a viral post is read from one origin.

Why that's risky: An edge copy of an edited post stays visible until it expires or is purged.

What gets added: A CDN serves the rendered page from the edge.

Trade-offs: A longer edge TTL helps viral posts but delays edits; purge-on-publish fixes that.

Stage 4: Rendering, Feeds and Limits

Render pages and update follower feeds in the background.

What was missing: Pages are rebuilt on demand, follower feeds are not updated and spam can flood publishing.

Why that's risky: If an author with a million followers published inside the request, publishing would stall.

What gets added: A publish queue with render workers that pre-render the page, purge the old copy and push the post to follower feeds, plus a rate limiter and monitoring.

Trade-offs: Fan-out on write makes follower reads cheap but costs work per follower; huge accounts are usually fanned out lazily.

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