About
You get the canvas, not the diagram.
Every box you add is judged, so you learn when it belongs.
Too much load: 10.1k/s arrives, but 5 instances handle about 10k/s. Run about 7 instances.
Interviewers never stop at “design Bitly.”
So neither do the problems: each step grows the design from the one before.
A busy day
Design Bitly.
ClientLoad balancerApp server×7Redis cachePostgresUsers around the world
Now make it global.
ClientCDNLoad balancerApp server×3Redis cachePostgresThe database dies
Now a DB node dies.
ClientCDNLoad balancerApp server×3Redis cachePostgresRead replica
Added at this stageResized at this stage
What we believe
System design is more than drawing boxes.
Understanding what Redis, Kafka or Postgres does is one thing. Knowing when to use them, what trade-offs they introduce, and when they become a bottleneck is another.
Litmus is built around that difference. We believe engineers learn architecture by making decisions, challenging assumptions, and understanding the consequences.
- Build, don't memorise.
- Learn by making architectural decisions yourself.
- Trade-offs over templates.
- There's rarely one perfect architecture. Context matters.
- Understand the why.
- Knowing why a design works matters more than copying a diagram.
Who makes it
Litmus is built by Amar Prakash Pandey. It's free. You sign in with GitHub, and your work is saved to your account.
Capacities are teaching estimates, not benchmarks.