Design a Comment System

Comment system inspired by Disqus and Reddit threads: comments are read far more than written, hot threads are cached and served from the edge, and spam checks run in the background.

Functional requirements

  • Show the comments for a page, newest or top first, with replies nested under their parent
  • Post a comment or reply; the author sees it immediately and others see it within seconds
  • Check every new comment for spam in the background and hide spam without blocking the author's post
  • Let a moderator remove a comment or a user, and make the removal visible quickly
  • Keep every comment durably, including after a page is deleted or archived
  • Limit how fast one user can post so a bot cannot flood a thread

Non-functional requirements

  • Comment list < 100ms p99 for hot threads, served from the thread cache or the edge
  • A new comment is visible to other readers within 5 seconds
  • Spam is hidden within 30 seconds of posting
  • Handle 4K requests per second at peak, with about 90% reads and 400 new comments per second
  • A busy thread must not overload the database: reads come from the cache and only misses reach the database
  • 99.99% durability for comments; scale to 1B comments
  • 99.9% availability for reading comments

How the design evolves

Stage 1: Query the Database for Every Page

See why reading all comments from the database on every page view does not scale.

What was missing: A page should not read all its comments from the database on every view.

Why that's risky: A popular story has thousands of identical comment loads per second.

What gets added: One server that reads a page's comments from the database on every view and saves each comment.

Trade-offs: Always current, but slow under load.

Stage 2: Comment Service and Cache

Separate reading from posting and serve threads from memory.

What was missing: Reading and posting share one path.

Why that's risky: A new comment can take a moment to show in a cached thread.

What gets added: A read service serving threads from a cache keyed by page, a post service that saves comments and replies, and a comment database as source of truth.

Trade-offs: Threads are served from memory; a new comment is visible after the cache is updated or expires.

Stage 3: CDN for Hot Threads

Serve the first page of hot threads from the edge.

What was missing: A breaking story sends everyone to the same thread.

Why that's risky: A cached first page hides a new comment for a few seconds.

What gets added: A CDN caches the first page of hot threads for a few seconds.

Trade-offs: A few seconds of delay is fine for a hot thread; deeper pages come from the cache.

Stage 4: Spam Screening and Limits

Screen new comments in the background and limit abuse.

What was missing: Spam stays visible and anyone can flood threads.

Why that's risky: Screening inside the post request would make every comment wait for a spam check.

What gets added: A moderation queue with spam workers that screen each new comment, hide spam and refresh the thread, a rate limiter and monitoring.

Trade-offs: Comments appear immediately and spam is hidden within seconds, trading a short window of visibility for fast posting.

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