System Design shouldn't be memorised. It should be experienced. Let's talk about it.

For too long, learning distributed systems has meant staring at static diagrams and hoping the concepts eventually click. You can recite CAP theorem, explain eventual consistency, draw a microservices diagram from memory, and still freeze when something breaks in production.

I know that feeling well. My background is in Mechatronics Engineering and I currently work as a software engineer at Gymshark. Distributed systems was never formally taught to me. I learned it the hard way, and that gap between theory and intuition is what pushed me to build Cascode, alone, around my full time job.

It’s a browser-based canvas where you assemble real AWS architectures, watch live message flows run through them, inject failures, and see what cascades.

No setup, no cloud bills, just a live environment to build and break things on purpose.

I’m early and actively building. Real-time collaboration, advanced search, and a lot more are on the roadmap: cascode.uk/roadmap

Try it free at cascode.uk. What would make a tool like this genuinely useful in your workflow?