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.
The catalogue database filled up at 0:15, when the cache entries expired together.
See whyBuild it, break it, understand why

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

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

Understand why
Read the chain of causes, from your own decisions to the p99 the client saw.
Four scenarios
- The Product Launch SpikeTraffic jumps to 50× on launch day, and every cache miss lands on the catalogue database.
- Orders That Must Not DuplicateA client retries a payment after a timeout, and the order gets written twice.
- The Read Replica That LiedA member posts, refreshes, and the replica behind the feed has not caught up yet.
- The Coordinator That Was Also a BottleneckEvery write to one viral product waits on one coordinator, and it runs out of room before the workers do.
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.
- 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 runSystem 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.
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.