System Design

What mastery looks like

This track contains 26 connected concepts rather than an unordered reading list. Mastery means you can move from vocabulary to mechanisms, predict how the system behaves under pressure, and support a design decision with code, measurements, or a failure-recovery exercise. For System Design, use the track description as the boundary: learn enough detail to reason clearly about architecture-level thinking: low-level design, scalability, distributed systems, event-driven design, and end-to-end case studies.

A useful explanation names the state involved, the operation that changes it, the resource or safety constraint, and the observable signal that tells you whether the mechanism works. Avoid stopping at product names. Compare at least two approaches, state what each optimizes, and identify what breaks first as scale, concurrency, latency, or uncertainty increases.

Suggested study sequence

Start with the core concepts at the top of the list and write a one-paragraph mechanism note for each. Continue through the core concepts by alternating explanation with an executable drill. Treat Concurrency Design, Booking & Inventory, Consistent Hashing, Consensus as integration work: they should combine earlier mechanisms rather than introduce disconnected facts.

At the end of each session, record one decision you can now make, one failure mode you can now predict, and one unanswered question. Revisit that question through the linked primary sources, then prove the answer in the Playground or a real repository. The track is complete when you can transfer the reasoning to an unfamiliar system, not when every page has been opened.

Roadmaps

• 12-Month Advanced AI Infrastructure
• Disk-First Databases & RAM
• Runtime — what every runtime has to do
• The Software Engineering Landscape (2026)
• LLD Practice
• HLD Practice

Concepts in this track