How to Scale From 1 Million to 100 Million Users in a System Design Interview

2025-09-23

One of the most common twists in a system design interview is when the interviewer says, “Okay, now scale this to 100 million users.” This is where strong candidates separate themselves by showing they can think about growth, bottlenecks, and trade-offs. Here’s how to approach that scaling question with confidence.

Step 1: Identify the First Bottleneck

Start by asking: “Where does this system break first?”

  • A single database?
  • Application servers?
  • Network throughput?

Spotting the weak link is the fastest way to show awareness.

Step 2: Add Horizontal Scaling

Instead of beefing up one machine, think about distributing load:

  • Multiple stateless app servers behind a load balancer.
  • Database sharding to split data across nodes.
  • Using content delivery networks (CDNs) to push static content closer to users.

Horizontal scaling is usually the safer, more realistic choice in interviews.

Step 3: Optimize Storage and Caching

At 100M users, databases become a constant bottleneck. Key strategies:

  • Add a read replica for high read workloads.
  • Cache hot data with Redis or Memcached.
  • Move large assets (images, videos) to object storage like S3.

This shows you understand how to relieve pressure on the database tier.

Step 4: Address Reliability and Fault Tolerance

A big system can’t afford to go down. Add:

  • Replication across regions.
  • Failover strategies in case of outages.
  • Message queues to smooth out traffic spikes.

Step 5: Re-Evaluate Trade-Offs

At smaller scale, consistency might be easy. At massive scale, you may need to shift to eventual consistency. Say it out loud. Interviewers want to see that you understand the reality of trade-offs at scale.

Step 6: Communicate Clearly

Don’t just throw buzzwords. Walk through scaling step by step. Show the interviewer you’re deliberate, not just memorizing patterns.

Pro Tip

Practicing scaling scenarios ahead of time makes this much easier. Tools like StealthCoder include system design prompts where you start small, then get challenged to scale up. It’s a great way to rehearse the exact twist you’ll face in real interviews.

The honest play

You've read the playbook. Now make sure you pass the live OA.

Knowing the patterns isn't the same as solving them under a timer with a proctor watching. StealthCoder is the hedge: an AI overlay invisible during screen share. It reads the problem on screen and surfaces a working solution in under 2 seconds. Built by an Amazon engineer who used it to pass JPMorgan's OA and system design loop. Works on HackerRank, CodeSignal, CoderPad, and Karat.

Hedge your live OA
Invisible during screen share
Get it