How This Course Works
You'll learn to
- -Understand how the course is organized into tiers, modules and chapters
- -Know what happens at the end of a chapter, and how reading connects to the HLD Lab
- -Start with a clear habit: read, check, then build
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. Highlights are saved on this device only. Log in to save them to your account instead.
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 them. Every chapter teaches one concept, then hands you off to a real level in the HLD Lab where you build it. HLD stands for High-Level Design: deciding how the large parts of a system, such as servers, databases and caches, fit together so it works for many users.
An Analogy: Learning to Cook
A recipe book alone does not teach you to cook, and neither does being thrown into a kitchen with no instructions. People learn fastest by reading how to make one dish and then making it straight away. This course is arranged that way: read one idea, then use it in the Lab before you forget it.
The Shape of the Course
The course is organized into six tiers. Each tier holds a few modules, and each module holds a handful of chapters. Tiers get progressively harder. Foundations assumes no prior knowledge, and by the time you reach Global Scale and 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 and Performance: databases, caching, rate limiting, sharding.
- -Tier 3, Distributed Systems Core: consistency, asynchronous messaging, real-time systems, APIs.
- -Tier 4, Scale and Reliability: storage at scale, distributed transactions, microservices, observability.
- -Tier 5, Global Scale and Capstone: multi-region architecture and full case studies.
The Loop
Every module after this one ends with a Lab Bridge: a card telling you exactly which HLD Lab levels apply what you just read. Take the caching module as an example. You read what a cache is and when it helps, and the bridge points you to a Lab level for a read-heavy system where a cache keeps the database from being overwhelmed. The loop is: read a module's chapters, take each short check-yourself quiz, then solve the linked levels. Come back, read the next module and repeat. By the time you reach the capstones, the building part will feel familiar, because you have practiced every piece of it.
You do not have to finish reading before you touch the Lab. If a module'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 denser reference material. The course text around them gives you the narrative and the order.
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."
Discussion0
Join the Discussion
Sign in to leave comments, reply to others, or like insights.
No comments yet. Be the first to start the thread!