system-design
Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "design Twitter", "design Uber", "design a news feed", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs (TinyURL, feeds, chat) and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.
- Version
- 1.4.1
- License
- MIT
Pinned to revision 4f7124e6049e, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/system-design/SKILL.md
- skills/system-design/references/building-blocks.md
- skills/system-design/references/common-designs.md
- skills/system-design/references/database-scaling.md
- skills/system-design/references/estimation-numbers.md
- skills/system-design/references/four-step-process.md
- skills/system-design/references/reliability-operations.md
Every link opens the file at its source, pinned to the revision this page describes.