Design a Link-in-Bio Page

Link-in-bio service inspired by Linktree: each creator has a public page of links that is served from the edge, edits are saved to a database, and click analytics are counted in the background.

Functional requirements

  • Show a creator's public page of links, loading fast for anyone who opens the profile link
  • Let a creator add, reorder, edit and remove links and change the page's look
  • Count clicks on each link and show the creator the totals
  • Let a creator see how many people viewed their page over time
  • Keep every creator's page and links durably
  • Limit how often a page can be edited or hit by one client, to stop abuse

Non-functional requirements

  • Page load < 100ms p99 for visitors, served from the CDN or page cache
  • An edit is visible to visitors within 30 seconds
  • Handle 10K page views per second at peak and 10 edits per second
  • Click counts may lag by up to a minute, but no click is lost (counted through a queue)
  • 99.99% availability for public pages, even if the editor is down
  • Scale to 50M creators with pages that rarely change, so almost every view is a cache hit
  • 99.99% durability for page and link data

How the design evolves

Stage 1: Query the Database for Every Visit

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

What was missing: A public page should not be rebuilt from the database on every visit.

Why that's risky: A famous creator sends thousands of visitors per second to one page, all running the same query.

What gets added: One server that reads a creator's links from the database on every visit and saves edits.

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

Stage 2: Page Service and Cache

Separate viewing from editing and serve pages from memory.

What was missing: Viewing and editing share one path.

Why that's risky: An edit can take a moment to show in the cache.

What gets added: A page service reading from a cache keyed by handle, an editor service and a profile database as source of truth.

Trade-offs: Pages are a few seconds stale after an edit.

Stage 3: CDN at the Edge

Serve public pages from the edge so a famous creator never overloads us.

What was missing: A famous creator's spike still reaches our servers.

Why that's risky: An edited page can show the old links until its edge copy expires or is purged, and a click served entirely from the edge would never be seen by us.

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

Trade-offs: Page views are cached at the edge, but clicks go through our redirect endpoint so they can be counted; purge on edit keeps pages fresh.

Stage 4: Click Analytics and Limits

Count clicks in the background and protect editing.

What was missing: Clicks are not counted and bots can create spam pages.

Why that's risky: Counting each click with a database write at 10K clicks/s would crush the database.

What gets added: The page service records each link click as an event on a queue before redirecting; workers count clicks per link in batches. A rate limiter on edits and page creation, and monitoring.

Trade-offs: Click counts lag by up to a minute in exchange for batched writes.

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