System design
This site’s full system-design curriculum (fundamentals → building blocks → HLD → LLD → deep dives) lives under /dsa/system-design. Use this page as a map: start here, then drill into the links that match your loop (phone screen vs onsite vs take-home).
System design curriculum (start here)
Learning order: fundamentals, building blocks, case studies, LLD, Kafka/Redis/Postgres deep dives.
Interview framework (RESHADED)
Step-by-step shape for any design question: requirements, estimation, API, data, scale, failure modes.
System design round playbook
Senior spoken arc: users → API → data → scale → failure → deep dive.
Master 90% syllabus (SDE3+)
Maps DSA + HLD/LLD + behavioral to this site—including React / Node / Next / AWS lanes.
Quick path by goal
| Goal | Go to |
|---|---|
| First principles | CAP / PACELC, consistency models, latency vs throughput |
| Building blocks | API gateway, load balancer, caching, sharding, rate limiter |
| Case studies (HLD) | URL shortener, news feed, YouTube, payments — full list in curriculum |
| OOD / LLD | LLD exercises (parking lot, elevator, LRU cache, …) |
| Store internals | DynamoDB, Redis, Postgres, Kafka |
| Product stack + data | /databases (RDS, DynamoDB, caching, CDC/outbox), /backend, /performance |
| Ship & run | /devops (CI/CD, Docker, Kubernetes, AWS patterns) |
How this fits the rest of the site
/system-design (this page)
│
└──► /dsa/system-design/... ← primary content tree
│
└──► /interview/topics/... ← round playbooks & syllabus
│
└──► /databases, /backend, /frontend, /performance, /devops
↑ concrete AWS / Node / React trade-offsSee also
- DSA + system design mind-map — patterns + curriculum index
- /performance — tails, profiling, DB query path, cache/retry amplification
Mark this page when you finish learning it.
Spotted something unclear or wrong on this page?