# Learn system design by playing

> A reading and playing order that takes you from your first server to scaling data, surviving failures, and answering interview questions.

You learn system design fastest by watching a design break under traffic and then fixing it, so this path alternates between playing and reading. Each stage starts with a few minutes in Quorum, then sends you to the pages that explain what you just saw. Stop after any stage and you have a complete idea, not half of one.

## Stage 1: one server, one database

Play [Your first Company](https://wiki.playquorum.dev/tutorials/first-company.md) and then [Your first bottleneck](https://wiki.playquorum.dev/tutorials/first-bottleneck.md). You will see a single server hit its limit and learn to read the cards that tell you which Node is full. Read [Capacity, utilization, and queues](https://wiki.playquorum.dev/explanation/queues.md) to see why a Node gets slow well before it is full, and [Latency and percentiles](https://wiki.playquorum.dev/explanation/latency.md) to see why the average hides your slowest users.

## Stage 2: more servers, then a cache

Add a second server behind a [Load Balancer](https://wiki.playquorum.dev/components/lb.md), then put a [Cache](https://wiki.playquorum.dev/components/cache.md) in front of the [Database](https://wiki.playquorum.dev/components/database.md). Read [stateless app servers](https://wiki.playquorum.dev/patterns/stateless-app-servers.md), [cache-aside](https://wiki.playquorum.dev/patterns/cache-aside.md), and [vertical and horizontal scaling](https://wiki.playquorum.dev/patterns/vertical-and-horizontal-scaling.md). The guide [Survive a traffic spike](https://wiki.playquorum.dev/guides/survive-a-traffic-spike.md) shows the same ideas under pressure.

## Stage 3: when the database is the limit

Add a [Read Replica](https://wiki.playquorum.dev/components/replica.md) and a [Connection Pooler](https://wiki.playquorum.dev/components/pooler.md). Read [read replicas](https://wiki.playquorum.dev/patterns/read-replicas.md), [replication strategies](https://wiki.playquorum.dev/patterns/replication-strategies.md), and [sharding](https://wiki.playquorum.dev/patterns/sharding.md), then [consistent hashing](https://wiki.playquorum.dev/patterns/consistent-hashing.md) for how a key finds its server. [Scale the database](https://wiki.playquorum.dev/guides/scale-the-database.md) walks through the order of moves.

## Stage 4: work that can wait

Put a [Queue](https://wiki.playquorum.dev/components/queue.md) and a [Worker](https://wiki.playquorum.dev/components/worker.md) behind slow jobs. Read [queue load leveling](https://wiki.playquorum.dev/patterns/queue-load-leveling.md), [publish-subscribe](https://wiki.playquorum.dev/patterns/publish-subscribe.md), and [idempotency keys](https://wiki.playquorum.dev/patterns/idempotency-keys.md), since a queue that retries needs a request that is safe to repeat.

## Stage 5: failures

Play through [Your first incident](https://wiki.playquorum.dev/tutorials/first-incident.md), then read [How incidents work](https://wiki.playquorum.dev/explanation/incidents.md) and [Errors and retries](https://wiki.playquorum.dev/explanation/errors-and-retries.md). The [retry storm guide](https://wiki.playquorum.dev/guides/stop-a-retry-storm.md) shows how a retry policy turns a short slowdown into an outage. Then read [timeouts](https://wiki.playquorum.dev/patterns/timeouts.md), the [circuit breaker](https://wiki.playquorum.dev/patterns/circuit-breaker.md), and [load shedding](https://wiki.playquorum.dev/patterns/load-shedding.md).

## Stage 6: put it into words

Read [System design concepts](https://wiki.playquorum.dev/explanation/system-design-concepts.md) for the whole map, then try the [system design interview questions](https://wiki.playquorum.dev/guides/system-design-interview-questions.md). Each one gives you the requirements, the load estimate, the design, and what breaks, and tells you what to build in the game to see it.

## Common questions

### Do I need to know how to code to learn system design?

No. System design is about which pieces to use and how they fit together, so you need to know what a server, a database, and a request are, and nothing more. Quorum teaches the rest by showing requests flow through the pieces you place.

### How long does it take to learn system design?

The core ideas fit into a few focused weeks. Playing each stage for twenty or thirty minutes and reading the linked pages is enough to hold a conversation about scaling a web service, and later stages give you the depth that senior interviews ask for.

### Is Quorum free?

Yes. It runs in your browser with no account and no download, and the source code is open.

Source: https://wiki.playquorum.dev/tutorials/learn-system-design
