Migrating 400K Users Without Downtime
A three-phase event-driven cloud migration off a strained monolith — preserving course history, progress, and revenue for half a million learners while cutting infrastructure costs in half.
Real projects with measurable results. Each case study includes the challenge, the approach, the actual implementation, and the lessons learned — because context matters as much as outcomes. Client names withheld where engagements are still under NDA.
First case study is live with full context. NDA-friendly versions of the others are available on request.
A three-phase event-driven cloud migration off a strained monolith — preserving course history, progress, and revenue for half a million learners while cutting infrastructure costs in half.
A car insurance startup with plenty of ideas and no infrastructure to test them. Built a microservices + feature-flag platform that let product run experiments in days, not quarters — 25% revenue lift across the first three.
Transformed a brand's blog division from an SEO funnel into an independent business line — capable of signing international branded-content agreements. Automated planning-to-publishing workflow lifted throughput 200%.
Every project is different, but the discipline is the same. I look at the business problem first, evaluate trade-offs honestly (including the boring option), and then build for what's actually likely to happen — not what could theoretically scale forever.
# ADR 0042: Migration strategy ## Context Legacy Magento monolith. 400K users. Revenue-critical. No downtime budget. ## Options evaluated - Upgrade in place // drifted, rejected - Optimize old vendor // costly, rejected - Parallel rebuild // chosen ✓ ## Decision Build cloud-native in parallel. MVP first → phased migration. ## Trade-offs + Existing revenue protected + No big-bang risk - Two systems to operate during transition ## Outcome 99.99% migration accuracy. -50% infra cost. 0 rollbacks.
Evenings (IST) and weekends, I share what I've learned with engineers building production systems. Architecture reviews, an honest second opinion, or just a sounding board — happy to help where I can.