SystemForge
Interactive system-design laboratory (teaching app)
Interface Gallery (13 Screens)













Home:Landing: what you will learn and the roadmap.
System Overview
"Instead of reading about caching, you flush the cache and watch the database fall over, then turn on request coalescing and watch it recover." Every topic follows one loop: theory, manipulate, observe metrics, break it, compare trade-offs. It ships forty system labs (each with overview, requirements, estimation, architecture, live demo, failures, scaling, observability, challenges and interview tabs), about 107 scored challenges, a drag-and-drop architecture canvas that can be run under load, a code playground, a step-by-step URL-shortener sandbox, a capacity calculator, and three real mini-systems you can bring up with Docker Compose. Progress stays in the browser; nothing leaves the machine.
Infrastructure & Stack
Next.js monorepo (apps/web), deterministic discrete-event simulation engine (packages/engine, 549 tests), Docker Compose mini-systems
Container Topology & Ports
From the mydocker dashboard: type "systemcraft" then "up", then "open".
Complete Flow & Screen Breakdown

Landing: what you will learn and the roadmap.

Labs grouped by Fundamentals, Building Blocks and Distributed Systems.

The forty system designs, grouped (core distributed, coordination and real-time, transactional and interactive).

Architecture canvas, empty: palette of component types, undo/redo, auto-layout, save/load JSON.

Code playground: eight exercises (LRU cache, token bucket, consistent-hash ring, base62 IDs, backoff with jitter, trie autocomplete, task pool, lease lock).

The three real mini-systems (Docker Compose).

Sandbox "URL shortener: grow it under load": seven steps from launch to sharding.

A concept lab (Caching): move the controls and watch hit rate and database load respond.

One system (URL shortener) with its tabbed design.

"Naive starter" loaded onto the canvas, ready to validate and run under load.

Step 2 (Add a cache): Redis in front of Postgres with the bottleneck still on the API tier, plus estimated cost.

Running the tests against the starter code: "0 of 8 passed" with each failing case named. Code runs in a sandboxed Web Worker with a 3-second timeout.

Capacity calculator for back-of-envelope estimates.