Course contentsShow
← System Design
Lesson 18 of 1,9191. System Design Mindset and First PrinciplesFree lesson

Prioritizing Requirements Under Constraints

Learn to balance competing requirements when you cannot optimize for everything simultaneously.

Prioritizing Requirements Under Constraints

What You'll Learn

You'll learn how to make smart tradeoffs when you can't satisfy all requirements perfectly due to real-world limits like time, budget, or technology.

The Reality of Constraints

In system design, you'll never have unlimited resources. You can't build a system that's simultaneously:

  • Infinitely fast
  • Perfectly consistent
  • Endlessly scalable
  • Completely secure
  • Deployed tomorrow
  • Built for free

Something always gives. Your job is to decide what gives based on what matters most.

The Prioritization Framework

Think of system requirements like features on a dream car. You want speed, fuel efficiency, cargo space, luxury, and affordability—but a Ferrari isn't a minivan, and a minivan isn't a Ferrari. You must rank what matters most for your specific use case.

Ask these questions:

  1. What's the core user need? If you're building a messaging app, delivery speed matters more than perfect message ordering.

  2. What's the business priority? A startup might prioritize fast launch over perfect reliability—you can improve later.

  3. What are the actual constraints? Limited budget? Three-month deadline? Small team? These force choices.

  4. What's the acceptable compromise? Can users tolerate 100ms extra latency if it means 99.9% availability instead of 95%?

Example in Practice

Imagine designing a photo-sharing app with limited resources:

  • Must-have: Users can upload and view photos (functional requirement)
  • High priority: Fast uploads (performance)
  • Medium priority: Handle 10x growth (scalability)
  • Lower priority: Sub-millisecond global consistency (nice-to-have)

You'd build the core upload feature first, optimize for speed second, and perhaps accept eventual consistency (photos appear within seconds, not instantly everywhere) to save complexity.

Key Takeaway: System design is the art of strategic compromise—identify your constraints, rank your requirements by impact, and consciously choose which tradeoffs serve your users and business best.