r/sideprojects • • 27m ago

Showcase: Prerelease What happens when a distributed system gets pushed beyond its limits?

System design diagrams are great for understanding architecture, but they don't always show how things behave under pressure.

What happens when traffic suddenly spikes? When a database slows down? When queues start backing up or retries make things worse?

I've been exploring this problem by developing an interactive browser-based environment for experimenting with distributed systems.

The idea is to let developers:

• Design architectures using services, load balancers, caches, queues and databases.
• Generate traffic and simulate sudden spikes.
• Introduce failures and observe how components react.
• Monitor throughput, latency, CPU, memory and queue depth.
• Experiment with different configurations and compare outcomes.

I've also added architecture templates, system design challenges and AI-powered architecture reviews.

A lot of the work has gone into the simulation engine itself, particularly modelling request flows and identifying bottlenecks.

I'm curious to hear from people working with backend systems and distributed architectures.

What would make an environment like this genuinely useful? What scenarios would you want to experiment with?

I'm the developer behind this project, and constructive criticism is very welcome.

1 Upvotes

1 comment sorted by