How This Course Works
You'll learn to
- -Understand how this course is organized into tiers, modules, and chapters
- -Know what happens when you finish a chapter
- -Understand how reading connects to the HLD Lab
Tip: the highlighter is on - just select any text below to mark it. Use the highlighter button up top to change color or turn it off, saved just for you on this device.
Most system design material falls into one of two camps: dense theory with nowhere to apply it, or lab exercises that assume you already know the theory. This course is the bridge between the two. Every chapter teaches one concept, then hands you off to a real level in the HLD Lab where you actually build it.
The Shape of the Course
The course is organized into six tiers, each containing a few modules, each containing a handful of chapters. Tiers get progressively harder: Foundations assumes zero prior knowledge, and by the time you reach Global Scale & Capstone you are combining a dozen concepts into systems like Uber, Netflix, and Datadog.
- -Tier 0 - Orientation: this module. How to use the course and how to think about design problems.
- -Tier 1 (Foundations): the web, servers, and the three-tier architecture every app starts from.
- -Tier 2 - Data & Performance: databases, caching, rate limiting, sharding.
- -Tier 3 (Distributed Systems Core): consistency, async messaging, real-time systems, APIs.
- -Tier 4 (Scale & Reliability): storage at scale, distributed transactions, microservices, observability.
- -Tier 5 (Global Scale & Capstone): multi-region architecture and full case studies.
The Loop
Each chapter ends with a Lab Bridge: a card telling you exactly which HLD Lab level applies what you just read. The loop is: read a chapter, take the short check-yourself quiz if there is one, then go solve the linked level. Come back, read the next chapter, repeat. By the time you reach the capstones, the "building" part will feel familiar because you have already practiced every piece of it.
You do not have to finish reading before you touch the lab. If a chapter's Lab Bridge looks interesting, jump straight to it; you can always come back for the parts you skipped.
Some chapters embed a deep-dive from the ScaleDojo Wiki instead of re-explaining a concept from scratch, and you will see a small "Wiki" tag on those. The Wiki entries are more reference-dense; the course text around them gives you the narrative and the ordering.
You're onboarding onto an unfamiliar, poorly documented codebase at a new job. How does the "read then build immediately" loop this course uses apply?
"I'd read through as much documentation as I can find before touching any code."
"I'd read just enough to understand one specific piece, then make a small, real change against it right away, the same loop this course uses of a chapter followed immediately by its linked lab level. Reading everything before touching code means most of it gets forgotten before it's ever used. Reading and building in tight loops surfaces gaps in understanding immediately, while they're still cheap to fix, instead of weeks later when they're buried under new work."