❌ – availability, consistency, latency, durability. ✅ Do use the repo’s trade‑off tables to justify decisions (e.g., “We chose eventual consistency for user timeline to achieve 99.99% availability”).
| Folder | Content | |--------|---------| | /diagrams | High‑level architecture visuals (great for quick revision) | | /blueprints | Step‑by‑step design walkthroughs for 15+ common products | | /cheatsheets | Latency numbers, database sharding formulas, trade‑off matrices | | /components | Deep dives on load balancers, caches, message queues, etc. | alex wu system design github