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

Scalability Requirements: Growth Expectations

Understand scalability as the ability to handle growth in users, data, and traffic over time.

Scalability Requirements: Growth Expectations

What you'll learn: How to think about a system's ability to grow with increasing demand over time.

What Is Scalability?

Scalability is your system's ability to handle growth—more users, more data, more requests—without breaking or becoming unusably slow. Unlike performance requirements (which focus on how fast your system responds right now), scalability asks: "What happens when we go from 100 users to 100,000 users?"

Think of scalability like a restaurant. A small café might serve 20 customers perfectly at lunch. But what happens when 200 people show up? If the kitchen, seating, and staff can't adapt, service grinds to a halt. A scalable restaurant has a plan: add tables, hire more cooks, or open a second location.

Why Growth Expectations Matter

When identifying non-functional requirements for a system, you must ask:

  • How many users do we expect today? In six months? In two years?
  • How much data will we store initially versus eventually?
  • Will traffic be steady or have massive spikes (like Black Friday sales)?

A system designed for 1,000 users might use a single server. But if you expect 1 million users, you need a completely different architecture from day one—multiple servers, load balancers, distributed databases.

Scalability vs Performance

Don't confuse these! A sports car (high performance) goes fast with one driver. A city bus (scalable) handles many passengers. You might need both: fast responses and the ability to serve millions.

Key Takeaway: Scalability requirements define how your system must grow—anticipating future user counts, data volume, and traffic patterns so you design the right architecture from the start, not scramble to rebuild later.