Stop memorising system design. Break a design and see why it failed.

Wire an architecture in your browser, send traffic through it, and read the chain of causes when it fails.

Free. No account. Runs in your browser. About 5 minutes.
The Product Launch Spike50× the usual traffic0:17
p99 at client428 msbudget 200 ms
Product Launch Spike50× traffic 0:17
p99428 msbudget 200 ms

The catalogue database filled up at 0:15, when the cache entries expired together.

See why

Build it, break it, understand why

The Syslern canvas while building: shoppers, a load balancer, a service and a cache are wired, and the catalogue database is being connected.

Build

Place a load balancer, services, caches and databases on the canvas, then wire them together.

A replay of the run: the catalogue database is full and the p99 chart crosses the 200 ms budget at 428 ms.

Break

Run the scenario and replay it second by second until one node gives out and the fault runs back to the client.

The chain of causes after a run that broke, with a question about why it happened.

Understand why

Read the chain of causes, from your own decisions to the p99 the client saw.

Four scenarios

Endless Run

You are the only engineer at a company whose traffic grows every week. Keep it up without the bill running away, and read the postmortem after every outage.

Weekly trafficWeekly costIncident and postmortem
week 1week 24
  • week 6traffic spiked
  • week 10catalogue-db got slower
  • week 14render-service went down
  • week 18the network split
  • week 22cache was flushed

Under the hood

  • 20 components
  • 4 scenarios
  • Deterministic: the same seed gives the same run
  • p99 is measured, not estimated

It does not model hardware, so it shows how a design behaves, not how many machines production needs.

Open a sample run
System design is usually learned from diagrams that never have to take any traffic. I built Syslern so you can watch a design fail and read why, long before one of yours fails in production.
Robert, who builds Syslern

For interviewers

Interview mode does not exist yet.

You and the candidate open the same canvas. The candidate designs the system. You inject a failure, a slow database or a lost availability zone, and you both watch how the design behaves.

Write to hello@syslern.com if you run system design interviews. You will get one email when interview mode works, nothing before that.

Questions

Is it free?
Yes. No account, no card.
Do I need an account?
No.
Where does my design live?
In your browser. Your designs never leave it.
How accurate is the simulator?
A deterministic discrete-event simulation with real queues, timeouts and retries. It teaches behaviour; it does not size your production.
What is not built yet?
Team interviews, and accounts that sync across devices.

Break a system on purpose, then find out why.

Start the 5-minute tutorialFree. No account. Runs in your browser. About 5 minutes.