Level 0 of 13 · about 1 week
How system design works
The words, the goals and the habit of doing the numbers first. Every later level uses this one.
Modules
Core: everyone needs it. Common: most jobs use it. Specialist: optional depth, safe to skip on a first read.
1
What system design is
What a design answers, how it differs from code, and what interviewers look for
Core 9 parts · about 2 hours
2
Requirements and scope
Asking the right questions, turning vague words into numbers, and deciding what to leave out
Core 9 parts · about 2 hours
3
Back-of-the-envelope estimation
Requests per second, storage, bandwidth, latency and uptime, worked with round numbers
Core 9 parts · about 3 hours
4
Reliable, scalable, maintainable
The three goals of every design, how load and speed are described, and why percentiles matter
Core 9 parts · about 3 hours
5
Trade-offs and architecture characteristics
The qualities a system can have, how to pick the few that matter, and how to choose the least worst design
Core 9 parts · about 3 hours
6
The four-step design framework
Understand, draw, go deep, wrap up: a method for any design question, with a time plan and a full example
Core 9 parts · about 3 hours
7
Scale from zero to millions of users
The ladder of changes a system goes through as it grows, from one server to many data centres
Core 10 parts · about 4 hours