System Design HLD-00.03
How to use this track
A map of the system design track: the modules, the three levels, how every lesson is built, and how to practise with full design case studies.
The big idea
System design can feel like an endless list of buzzwords: sharding, consensus, CQRS, consistent hashing. It is easier than it looks, because almost everything is built from a few foundations and a dozen building blocks, combined over and over. This track is ordered so that each idea rests on ones you already have.
Think of it like learning to cook. First you learn heat, knives and seasoning (foundations). Then you learn techniques like roasting and braising (building blocks). Only then do whole menus (case studies) make sense, and you can invent your own.
How it works
Step 1: The map
Each station below is a module. Stations you can open are lit; dots show lessons you have finished on this device.
Step 2: Five stretches of track
- Foundations (modules 0 to 2): how computers and networks behave, the latency numbers that drive design, and back-of-the-envelope estimates. Everything later leans on these.
- Building blocks (modules 3 to 7): APIs, load balancers, caches, databases and how data is scaled out. These are the components every architecture is assembled from.
- Distributed systems (modules 8 to 11): consistency and consensus, queues and streams, transactions that span services, unique IDs and locks. What changes when one machine becomes many.
- Running and shaping systems (modules 12 to 17): reliability, observability, architecture styles, search and geo data, security and infrastructure.
- Practice (modules 18 and 19): a framework for design interviews, then 23 full case studies such as a URL shortener, a chat app or a video platform.
Step 3: Three levels
Each lesson is marked beginnerNo background needed beyond basic programming and using the web., intermediate or advanced. Beginner lessons assume no prior system design. Intermediate lessons assume the building blocks. Advanced lessons dig into the internals and edge cases that come up in senior design reviews and interviews. Skipping ahead is fine; each lesson lists what it builds on at the top.
Step 4: The rhythm of every lesson
Every lesson follows the same pattern, so you always know where you are:
- The big idea: the concept in plain words, with an everyday picture.
- How it works: the mechanics, step by step, with glowing diagrams you can step through.
- Try it: a hands-on simulator or exercise. Change the inputs and watch what happens.
- Trade-offs: when to use it and when not to.
- Common mistakes: the traps people actually fall into.
- In the wild: a real engineering story or paper, summarized and linked.
- Check yourself and Recap: a short quiz with explanations and the five points to remember.
Going deeper
If you are preparing for interviews
Work through the foundations and the building blocks first, then go straight to the case studies module and practise designing a full system out loud: requirements, estimates, a high level design, then deep dives. Come back to the distributed systems theory when a case study raises a question you cannot answer. Start with Back-of-the-envelope estimation : estimation is the step candidates most often skip.
If you are building something real
Read the foundations, then jump to whichever building block your project needs next. Each lesson stands on its own and links to the lessons it depends on.
Common mistakes
- Memorizing architectures instead of reasons. Interviewers and real systems both change the requirements; the reasons transfer, the diagrams do not.
- Skipping the foundations. Latency numbers and estimates are what make the rest of your answers believable.
- Reading without doing. Use the simulators and answer the quizzes before you look at the explanations.
Check yourself
-
Which part of every lesson gives you a hands-on simulator?
Show answer
B. Try it The Try it section has the interactive widget for the lesson's idea.
-
You are preparing for a system design interview in a month. What order makes sense?
Show answer
B. Foundations and building blocks, then case studies Case studies combine the building blocks, so learn those first, then practise full designs.
-
Where is your progress on this track stored?
Show answer
B. In this browser only Progress is saved in your browser's local storage. There are no accounts, and clearing site data resets it.
Recap
- The track runs from foundations to building blocks, distributed systems, operations and full case studies.
- Lessons are beginner, intermediate or advanced, and each lists what it builds on.
- Every lesson follows the same rhythm: idea, mechanics, try it, trade-offs, mistakes, real story, quiz.
- For interviews, learn the building blocks, then practise case studies out loud.
- Progress is saved in your browser only.