Part 1 of 9 · 1 min read
Why this page comes first
In this module you will
- Say in one sentence what a system is, and what a design says about it.
- Explain the difference between designing a system and writing its code, with an example of each.
- Name the usual parts in a design (client, server, data store, cache, queue) and what each one is for.
- Explain why every design choice is a trade-off, and say what is gained and what is lost.
- Say what an interviewer looks for in a system design interview, and which habits count against a candidate.
Every later page in this path asks the same kind of question: "Given what this system must do, which parts should it have, and why?" This page gives that question a plain shape.
No code is needed. Numbers appear only where they help. Where a number is made up to show an idea, the page says so.