Sign in
Skip to solution
hardSystem Design

How would you design a system that scales to millions of users on AWS?

497 views
01

Understand the problem

Iterative AWS scaling from single host to millions: LB, cache, DB replication, sharding, and async.

awsscalinguserslbcdnshardingreplicationhorizontal-scaling
02

Attempt it yourself

Sketch your approach before reading the solution — that's what interviews test.

Nudge consolestandby

Stuck? Beam a request up — the console returns a conceptual nudge that guides your logic without spoiling the implementation.

03

Study the solution

Step 1: Use Cases, Constraints, Assumptions, Back-of-Envelope

Use cases

We'll scope to handle only the core flows that expose the bottlenecks; everything else is deferred.

  • User signs up / logs in — auth on stateless API, session in Redis, email verify async.
  • User reads feed/profile — cache-first, C

Solution ready — 2 min read

Classified // press E to declassify

04

Join the discussion

Discussion (0)

Sign in to join the discussion.

No responses yet. Be the first to share what you think.

Transmission complete // awaiting log

KEEP THE
STREAK ALIVE.

Dossier 74 of 99 decoded in the System Design track. One more won't hurt.

Back to track