Trade-offs Over Best Practices
What you'll learn: Why context matters more than blindly following "best practices" in system design.
The Core Idea
In system design, there is no universal "best" solution—only the solution that best fits your specific requirements and constraints. Every design decision involves giving up something to gain something else. A choice that's perfect for one system might be terrible for another.
Think of it like choosing a vehicle: A sports car isn't "better" than a pickup truck in absolute terms. If you're racing on a track, the sports car wins. If you're hauling furniture across muddy terrain, the truck is superior. The "best" choice depends entirely on what you need to do.
Understanding Trade-offs
When someone says "you should always use microservices" or "caching is a best practice," they're ignoring context. Consider these real trade-offs:
- Caching improves latency but adds complexity and potential staleness
- Microservices enable independent scaling but increase operational overhead
- Strong consistency ensures correctness but limits availability (remember your consistency requirements lesson!)
- Normalization reduces data redundancy but may slow down read-heavy queries
Design for Your Context
Your job isn't to memorize solutions—it's to understand the trade-offs and choose based on:
- Your functional requirements (what must it do?)
- Your non-functional requirements (how fast, how reliable, how scalable?)
- Your team's expertise
- Your budget and timeline
- Your growth expectations
A startup with 1,000 users needs different choices than Netflix with 200 million users. Don't prematurely optimize for scale you don't have (remember YAGNI!).
Key Takeaway: Every design decision is a trade-off between competing priorities. There are no universal "best practices"—only informed choices that balance the specific requirements, constraints, and context of your system.