Skip to main content
System Design LabZHIMA / SYSTEMS

LEARN BY MAKING DECISIONS

From one request.
To a resilient system.

From a single request to a system ready to grow.

12 lessons / 12 experiments / Bilingual · Free · No sign-in

THE CAMPUS RESOURCE SERVICECOURSE CASE
Capstone: the exam-week resource service — System relationship diagramExam-week demand → Web edge; Web edge → App cluster; App cluster → Cache; App cluster → Database; App cluster → Notify queue; Notify queue → Notify workerExam-week demandWeb edgeApp clusterCacheDatabaseNotify queueNotify worker
Submit a reviewable design4 / 4

Trace the path

Step through how the system works

Change conditions

Tune parameters, inject failures, compare

Show understanding

Pass constraints and explain costs

Your learning path

201 min

One evolving service. A complete path through system design decisions. Basic HTTP and database knowledge helps. No distributed systems experience required.

Foundations

Trace a request and estimate exam-week peak traffic and concurrency.

Scaling

Calculate spare capacity after an API failure and how many database reads caching saves.

Data

Explain slow queries, stale reads, and hot spots using access paths, replica lag, and shard load.

Reliability

Estimate when a queue will drain, judge whether retries add pressure, and measure what users experience.

Design Practice

Explain a choice during a network partition and propose a design that meets failure and budget constraints.

DESIGN IS A SERIES OF TRADEOFFS

Draw the system. Explain the decisions.

Finish with traffic, failure and budget constraints, then save your results and design decisions.

Open capstone

Explain requirements, estimates, tradeoffs, recovery and assumptions that need validation. Saved in this browser.