About TryInfraLab
Most resources explain backend architecture with static diagrams and pseudocode. You read it, it makes sense in the moment, and then you close the tab.
TryInfraLab takes a different approach: every flow you see is backed by real infrastructure. Real object storage. Real message queue. Real background worker. Real database writes. Real timestamps from real servers.
The goal is to make the moment of understanding stick by letting you trigger it yourself.
Built by Swan
I am a lead engineer with a few years of experience building backend systems and working with engineering teams in remote startup environments. Most of that time has been spent trying to keep systems maintainable, delivery predictable, and engineers unblocked.
I built TryInfraLab on the side because I kept explaining the same backend patterns to people and realised talking through it only goes so far. Watching it run is better.
What is here now
Image Optimization Pipeline
Upload an image and watch it move through object storage, a message queue, a background worker that resizes and converts to WebP, a database write, and an SSE notification back to your browser.
What is coming
More flows are in the works, each covering a backend pattern that shows up repeatedly in production systems. Same format: real infrastructure, step-by-step, no simulations.