Hld High Level Design

The chapters in this module, in reading order.

#	Chapter
00	High-Level Design — The Five-Year-Old Version
01	Requirements to Architecture — from fuzzy ask to first sketch
02	Component Decomposition — splitting the city into clear zones
03	API Design at Boundaries — drawing the right roads between zones
04	Data Modeling and Storage — Pick the right warehouse before traffic starts
05	Sync vs Async Communication — Decide which roads must wait and which should move on
06	Load Balancing and Routing — The toll booth that decides who goes where
07	Caching at System Level — many small fast warehouses
08	Scaling the Read Path — add more lanes for readers
09	Scaling the Write Path — split the loading dock
10	Consistency and Replication — Which warehouse tells the truth
11	Failure Modes and Resilience — Draw the bad day too
12	Rate Limiting and Backpressure — Close the lanes before the city jams
13	Common HLD Archetypes — Four city plans interviewers keep reusing
14	AI System HLD Patterns — The city where compute is expensive and timing is everything
15	Honest Admission — The map is useful, but not complete