Design a QR Code Service

QR code service inspired by QR Code Generator and Bitly codes: dynamic codes point to a short link whose destination can be edited, scans resolve from the edge, and scan analytics are counted in the background.

Functional requirements

  • Create a dynamic QR code that points to a short link, and return the image to the owner
  • Resolve a scan to the current destination as fast as possible, from the edge when it can
  • Let the owner change a code's destination without changing the printed QR code
  • Count every scan per code (time, rough location, device) without slowing down the redirect
  • Show the owner scan counts over time
  • Never reuse or expire a code unless the owner deletes it, even if it was printed years ago
  • Limit how many codes and edits one account can create per minute

Non-functional requirements

  • Scan redirect < 50ms p99 for cached codes and < 150ms on a cache miss
  • A changed destination is live everywhere within 30 seconds (cache entries expire or are purged)
  • Handle 10K scans per second at peak and 100 code creates or edits per second
  • Scan counts may lag by up to a minute, but no scan is lost (counted through a queue)
  • 99.99% availability for scans: a printed code must keep working even if creation is down
  • Scale to 1B codes, never reused
  • 99.99% durability for code and destination records

How the design evolves

Stage 1: Query the Database for Every Scan

See why a database lookup on every scan does not scale.

What was missing: Resolving a scan should not query the database every time.

Why that's risky: A printed campaign code can be scanned thousands of times per second, and every scan runs the same lookup.

What gets added: One server that looks a code up in the database on every scan and redirects, and saves new codes.

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

Stage 2: Resolver Service and Cache

Separate scanning from editing and resolve from memory.

What was missing: Scanning and editing share one path.

Why that's risky: An edited destination can take a moment to take effect.

What gets added: A resolver service reading destinations from a cache keyed by code, a code service for creating and editing codes, and a code database as source of truth.

Trade-offs: A dynamic code is a short link whose destination can change, which is why scans must resolve through the service and not be embedded in the image.

Stage 3: CDN for Scans

Resolve popular codes from the edge so a campaign never overloads us.

What was missing: A big campaign sends thousands of scans at once.

Why that's risky: A cached redirect keeps pointing to the old destination until it expires.

What gets added: A CDN caches each code's redirect at the edge for a short time.

Trade-offs: A permanent (301) redirect is remembered by browsers forever, which breaks editing and hides repeat scans; a temporary (302) redirect with a short edge TTL keeps both working.

Stage 4: Scan Analytics and Limits

Count scans in the background and limit abuse.

What was missing: Scans are not counted and anyone can create malicious codes in bulk.

Why that's risky: Scans answered at the edge never reach our servers, so without edge logs most scans would go uncounted.

What gets added: The resolver puts every scan on a queue, and scans answered at the edge are reported to it in batches from the CDN's logs; workers count scans per code in batches. A rate limiter on code creation and monitoring.

Trade-offs: Counts lag by up to a minute in exchange for fast scans.

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