Skip to content
Katabench
Try free
Coming soon System Design Studio

Do not just draw a system.
Prove the design holds together.

Build architectures on an interactive canvas. Katabench checks the paths, boundaries, and redundancy that should be there, plus the dangerous bypasses that should not, then teaches you the tradeoffs behind the passing design.

Interactive access opens after grading is live 49 beta challenges Best on desktop

A short flow preview explains direction and handoffs. It is illustrative, not measured latency or a load test.
49
progressive challenges
23
provider-neutral components
Easy to Hard
one pressure at a time

The practice loop

Build. Check. Learn.

A system design prompt becomes deliberate practice when the diagram has a clear goal, immediate evidence, and a useful debrief.

01

Build

Click or drag provider-neutral components onto the canvas. Connect them, move private services into real boundaries, and keep the interaction fast without edge-type dialogs.

02

Check

Get deterministic feedback on required paths, forbidden bypasses, redundancy, fan-out, containment, and connection semantics. Failed rules come first.

03

Learn

Use progressive hints when you need them. A passing Submit opens the tradeoffs, failure modes, and operational signals behind the accepted design.

The difference

A diagram that has to mean something

Katabench understands what the boxes represent. It can reject a direct client-to-database route, an app path that skips the cache, a queue without redundant consumers, or a service drawn inside a VNet without actually belonging to it.

Feedback is deterministic and grouped by correctness, security, reliability, and observability. No aesthetic score. No black-box AI verdict.

The Cache the Hot Path canvas beside failed checks that explain the missing load balancer, cache, second app instance, and database replica.
Failed rules come first and name the structural property to fix.

Guided curriculum

Learn the primitives. Then build the product.

Nine fundamentals each pair one requirement with the pattern that solves it. Three build courses then carry one product each, a video platform, a URL shortener, and a file vault, through the decisions that appear as its traffic and responsibilities grow.

Series 01 · Fundamentals

One requirement, one canonical pattern

Each challenge states a problem and applies the building block that solves it: a trusted boundary, a highly available API, caching, queues, database failover, an edge, rate limiting, sharding, and search.

9 challenges

  1. 01

    Keep clients off the database

    Route Through the App

    Free Easy

    Put a trusted service between the client and the data so nothing queries the database directly.

    3 deterministic checks

  2. 02

    Survive an instance failure

    Scale the Web Tier

    Free Easy

    Load-balance redundant, stateless instances so the balancer reroutes around a failed one.

    9 deterministic checks

  3. 03

    Serve reads at scale

    Cache the Hot Path

    Free Medium

    Add cache-aside in front of the database and a standby replica behind it.

    12 deterministic checks

  4. 04

    Survive a database failure

    Survive a Database Failure

    Medium

    Stream changes to a promotable standby replica so a lost primary is not a lost product.

    8 deterministic checks

  5. 05

    Cut global latency

    Serve from the Edge

    Medium

    Cache static content at a global edge and keep the origin for what actually changes.

    9 deterministic checks

  6. 06

    Shed abusive traffic

    Rate-Limit at the Gateway

    Medium

    Count requests at the gateway against a shared store and reject overload before it reaches the app.

    12 deterministic checks

  7. 07

    Make it searchable

    Derive a Search Index

    Medium

    Project committed changes from the source database into a derived search index that queries read.

    12 deterministic checks

  8. 08

    Absorb a write spike

    Buffer the Write Spike

    Hard

    Decouple arrival from processing with a durable queue and a redundant worker pool.

    16 deterministic checks

  9. 09

    Scale past one database

    Shard the Database

    Hard

    Partition the data across shards and route each key to the shard that owns it.

    7 deterministic checks

Series 02 · Build a Video Platform

Evolve one product from catalog to operations

Carry the same video product through catalog scale, edge delivery, uploads, search, security, and observability.

8 challenges

  1. 10

    Establish the catalog boundary

    Build a Video Catalog

    Easy

    Keep video metadata behind a trusted Catalog API before the product begins to scale.

    3 deterministic checks

  2. 11

    Remove the single API failure

    Scale the Video Catalog

    Easy

    Put a load balancer in front of interchangeable Catalog API instances without reopening a database bypass.

    9 deterministic checks

  3. 12

    Relieve repeated metadata reads

    Cache the Video Watch Page

    Medium

    Add a metadata cache to every Watch API data path while preserving the scaled service tier.

    9 deterministic checks

  4. 13

    Separate control from media delivery

    Deliver Video from the Edge

    Medium

    Keep playback authorization behind an API while a CDN serves video from durable object storage.

    9 deterministic checks

  5. 14

    Move long work off the request path

    Process Video Uploads

    Medium

    Use signed object uploads, durable messaging, and redundant workers to absorb processing bursts.

    13 deterministic checks

  6. 15

    Create a searchable projection

    Build Video Search

    Medium

    Keep the metadata database authoritative while committed changes update search asynchronously.

    14 deterministic checks

  7. 16

    Protect privileged operations

    Secure Video Operations

    Hard

    Put moderation services, data, and secrets inside private boundaries reached through a VPN gateway.

    15 deterministic checks

  8. 17

    Explain asynchronous delays

    Observe the Video Pipeline

    Hard

    Collect broker and worker telemetry through OpenTelemetry so operators can follow work in Grafana.

    12 deterministic checks

Series 03 · Build a URL Shortener

Scale one tiny request a billion times

Carry a link shortener from its first trusted boundary to cached redirects, asynchronous click analytics, edge delivery, and full observability.

6 challenges

  1. 18

    Protect the links database

    Shorten the First Link

    Easy

    Put a trusted Link API between the browser and the data that every redirect depends on.

    4 deterministic checks

  2. 19

    Outlive one link's spike

    Survive the Viral Link

    Easy

    Load-balance a redundant redirect tier so one viral link cannot take every link down.

    9 deterministic checks

  3. 20

    Stop re-reading the same row

    Cache the Redirect

    Medium

    Cache the code lookup for a read-heavy skew and weigh 301 against 302 before browsers decide for you.

    12 deterministic checks

  4. 21

    Measure without slowing down

    Count the Clicks

    Medium

    Queue click events off the redirect path and let redundant workers fold them into counts.

    15 deterministic checks

  5. 22

    Beat the speed of distance

    Redirect from the Edge

    Medium

    Serve hot redirects from a global edge with TTLs that keep deletion and analytics honest.

    11 deterministic checks

  6. 23

    Prove where the time goes

    Observe the Shortener

    Hard

    Trace every tier through OpenTelemetry so slow regions and lagging counts become dashboards, not arguments.

    16 deterministic checks

Series 04 · Build a File Vault

Move heavy bytes without melting the API

Store, scan, and share user files with signed uploads, an event-driven malware scan, edge downloads, and a guarded admin plane.

5 challenges

  1. 24

    Get bytes out of the database

    Store the First File

    Easy

    Split immutable file bytes into object storage while the database keeps the metadata it can query.

    5 deterministic checks

  2. 25

    Free the request workers

    Upload Directly to Storage

    Medium

    Authorize at the API, then move gigabytes with short-lived signed uploads that bypass it.

    8 deterministic checks

  3. 26

    Never share unscanned bytes

    Scan Before You Share

    Medium

    Turn object-created events into redundant malware scans that gate sharing on a recorded verdict.

    14 deterministic checks

  4. 27

    Stop proxying downloads

    Download from the Edge

    Medium

    Let the Share API decide who may download while the edge network moves the bytes.

    10 deterministic checks

  5. 28

    Shrink the blast radius

    Guard the Vault

    Hard

    Put the admin plane, metadata, and signing keys behind a VPN inside real network boundaries.

    15 deterministic checks

Series 05 · Build a Notification Platform

Deliver at scale without ignoring consent

Move from trusted acceptance to asynchronous channel fan-out, preference enforcement, provider isolation, and delivery operations.

5 challenges

  1. 29

    Create a trusted acceptance boundary

    Accept Notification Requests

    Easy

    Let a Notification API validate and durably accept intent instead of exposing delivery data.

    5 deterministic checks

  2. 30

    Isolate provider latency

    Queue Notification Delivery

    Medium

    Acknowledge accepted work, then deliver through a durable asynchronous queue.

    9 deterministic checks

  3. 31

    Scale email, SMS, and push independently

    Fan Out Notification Channels

    Medium

    Publish once to a topic and give each channel an isolated consumer path.

    9 deterministic checks

  4. 32

    Apply opt-outs under campaign load

    Honor Notification Preferences

    Hard

    Put a shared preference cache backed by durable truth on every delivery path.

    12 deterministic checks

  5. 33

    Make delivery diagnosable and resilient

    Operate the Notification Platform

    Hard

    Combine redundant compute, managed provider secrets, and telemetry across asynchronous channels.

    20 deterministic checks

Series 06 · Build Real-time Chat

Keep millions of conversations connected

Scale long-lived connections, durable ordered messages, presence, attachments, secrets, and asynchronous observability.

5 challenges

  1. 34

    Secure the real-time boundary

    Establish a Chat Session

    Easy

    Terminate untrusted connections at a gateway and keep conversation policy in a Chat Service.

    6 deterministic checks

  2. 35

    Survive a connection-host deploy

    Scale Real-time Connections

    Medium

    Load-balance interchangeable gateways and move presence into shared leased state.

    7 deterministic checks

  3. 36

    Keep storage latency off socket loops

    Persist Chat Messages

    Medium

    Publish accepted messages durably and persist them with redundant ordered consumers.

    11 deterministic checks

  4. 37

    Keep media bytes off connection hosts

    Deliver Chat Attachments

    Medium

    Authorize through the API, upload directly with a signed grant, and read from the edge.

    10 deterministic checks

  5. 38

    Trace sockets through durable delivery

    Operate the Real-time Chat Platform

    Hard

    Unify connection scale, persistence, media, secrets, and cross-broker observability.

    18 deterministic checks

Series 07 · Build a Reliable Checkout

Move money through explicit failure states

Practice inventory reservation, idempotent payment, transactional outbox delivery, compensation boundaries, and reconciliation signals.

5 challenges

  1. 39

    Stop trusting browser totals

    Own the Checkout Command

    Easy

    Put pricing, identity, and order creation behind one trusted Checkout API.

    6 deterministic checks

  2. 40

    Avoid charging unavailable stock

    Reserve Before Payment

    Medium

    Commit a bounded inventory reservation before payment enters the asynchronous path.

    10 deterministic checks

  3. 41

    Make redelivery safe for money movement

    Make Payment Idempotent

    Medium

    Give every payment worker the same durable idempotency ledger and provider key.

    10 deterministic checks

  4. 42

    Close the database-to-broker loss window

    Publish Order Events Reliably

    Hard

    Relay a transactional outbox into independent fulfillment and receipt subscriptions.

    10 deterministic checks

  5. 43

    Explain every pending order

    Operate the Reliable Checkout

    Hard

    Combine redundant checkout, idempotent payment, outbox delivery, secrets, and stage-level telemetry.

    23 deterministic checks

Series 08 · Build a Social Feed

Balance write fan-out against read-time work

Build materialized timelines, a celebrity hybrid, moderation and search projections, edge media, and freshness operations.

5 challenges

  1. 44

    Own identity and visibility

    Publish the First Post

    Free Easy

    Keep canonical publishing behind a trusted Post API.

    6 deterministic checks

  2. 45

    Stop recomputing every feed read

    Fan Out Home Timelines

    Free Medium

    Project post events into replayable follower timelines with redundant workers.

    11 deterministic checks

  3. 46

    Cap worst-case write amplification

    Handle Celebrity Fan-out

    Free Hard

    Combine push timelines for ordinary authors with pull-time celebrity candidates.

    15 deterministic checks

  4. 47

    Derive policy and search without API dual writes

    Moderate and Index Posts

    Hard

    Build replayable moderation and search projections from committed content events.

    14 deterministic checks

  5. 48

    Operate every eventually consistent view

    Operate the Social Feed

    Hard

    Bring hybrid feeds, search, edge media, managed secrets, and freshness telemetry together.

    28 deterministic checks

Optional synthesis

Operate the complete upload pipeline

Bring networking, storage, messaging, secrets, and observability together after the focused lessons.

1 challenge

  1. 49

    Synthesize the whole operating model

    Operate the Upload Pipeline

    Optional capstone Hard

    Combine signed uploads, messaging, private boundaries, secrets, OpenTelemetry, and Grafana.

    34 deterministic checks

The advanced upload pipeline challenge with a virtual network containing APIs, workers, a message broker, and an OpenTelemetry collector, connected to object storage, secrets, and Grafana.
The optional capstone brings networking, messaging, storage, security, and observability together.

Standard component vocabulary

23 components. One visual language.

Design with capabilities, not one cloud vendor's catalog. Every lesson exposes only the choices that matter, while the shapes and meanings stay consistent across the curriculum.

Edge & network

  • Client
  • CDN
  • Load Balancer
  • API Gateway
  • VPN Gateway
  • Virtual Network
  • Subnet

Compute

  • App Service
  • Worker
  • Serverless

Messaging

  • Queue
  • Message Broker
  • Topic

Data & storage

  • Cache
  • Database
  • DB Replica
  • Search
  • Object Storage
  • Shared File Storage

Security & operations

  • Secrets Vault
  • OTel Collector
  • Grafana
  • Grafana Stack
A close view of the post-solve lesson for Cache the Hot Path, beside part of the passing topology.
Passing Submit opens the lesson; a green diagram is the start of the debrief.

The learning payoff

Passing is the start of the debrief

A clean Submit opens a puzzle-owned lesson explaining why the topology works, where it can fail, which signals matter in production, and which properties a diagram cannot establish.

In Cache the Hot Path, for example, the lesson moves beyond adding a cache into hit-rate math, cache-aside behavior, invalidation, stampedes, failure policy, and replica lag.

Honest grading boundary

What today's grade proves, and what it does not

The current beta grades architecture structure. We will not market a passing topology as proof that it scales until a reproducible capacity model can earn that claim.

Today's beta verifies

  • Required components and end-to-end semantic paths
  • Forbidden direct connections and bypass routes
  • Fan-out, participation, and structural redundancy
  • Real VNet and subnet containment
  • Request, messaging, storage, secrets, telemetry, and replication semantics

It does not yet prove

  • p99 latency, throughput, availability, or cost
  • Cache hit rate or working-set capacity
  • Queue depth or burst recovery time
  • Correct failover, authorization, or secret rotation

We are evaluating deterministic workload simulation with versioned scenarios and fixed seeds as the next grading tier. Real provisioned load tests belong in calibrated labs, not as a noisy interactive verdict for an abstract diagram.

Frequently asked questions

Is this an AI architecture review?

No. The rules are authored and deterministic. The same valid topology receives the same verdict, and feedback names the exact property that passed or failed.

Does a passing design prove it scales in production?

Not today. The beta grades structural properties. Its moving packet explains direction and reachability, not traffic or latency. A deterministic capacity simulator is a separate planned tier.

Do I need AWS, Azure, or GCP experience?

No. Components are provider-neutral capabilities such as load balancer, queue, object storage, secrets vault, and OpenTelemetry collector. The lessons teach the decision before the vendor product.

Is there only one correct diagram?

No. Rules grade properties such as safe paths, containment, redundancy, and forbidden bypasses. They do not compare pixels or require one exact layout.

How many challenges are in the beta?

Forty-nine. Nine fundamentals isolate the core patterns, then seven progressive build courses apply them to video, URL shortening, file storage, notifications, real-time chat, checkout, and social feeds. One optional hard capstone combines the operating concerns.

Can I build a design on my phone?

Mobile is review-only. The canvas is designed for deliberate desktop or laptop authoring, where dragging, connecting, and inspecting a topology stay precise.

What does it cost?

You can start building and editing in the browser without an account. Sign in to check and submit; six challenges are included with a free account, including an Easy-to-Hard Social Feed mini-course. The rest of the catalog is part of Katabench Pro.

Coming soon

The Studio is nearly ready

Explore the curriculum and interaction model today. The build link appears only after topology grading is live, so this preview can never send you into an unavailable challenge.

Explore Katabench

Get new puzzles and .NET tips in your inbox

A short note when fresh kata land, plus the C# and performance tricks behind the grading. No spam, unsubscribe anytime.