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.
Whether you are getting your first taste of backend systems, filling in mid-career knowledge gaps, or learning how experienced engineers approach system design, the format is the same: trigger it, watch it run, understand why each piece is there.
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 to give engineers at every stage a faster way to build intuition for backend systems. Talking through architecture only goes so far. Watching it run, with real timestamps and real failures, is better.
Roadmap
Available 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.
Possible coming flows
Auth Flow
Login, session management, JWT issuance, token refresh, and revocation, all running live so you can see every handshake.
Payment Pipeline
Charge initiated, webhook received, order confirmed. Watch how Stripe events drive your backend state machine in real time.
Traffic Spike
Sudden burst of requests hits your API. See rate limiting, queue backpressure, and graceful degradation respond in sequence.
Email Pipeline
Transactional email queued, delivered, bounced, and retried, with unsubscribe webhooks closing the loop automatically.