Flagship engagement · E-commerce · AWS · Azure · GCP
Modernising a high-growth commerce platform across AWS, Azure and GCP
ANS Commerce, a leading Indian e-commerce platform in the Flipkart group, running across three separate cloud environments, with workloads spread between AWS, Azure and GCP.
ANS Commerce · Flipkart groupNamed with the client's permission.3 clouds
AWS, Azure and GCP
EC2 → GKE
VM-to-container re-platforming
~30%
Cost reduction in confirmed scope
Principal-led
Senior engineering ownership
The challenge
Fragmented cloud environments, VM-heavy workloads and manual infrastructure changes were slowing delivery and driving cost — while inconsistent monitoring made problems hard to see before they hit the business.
Across three engineering workstreams for the client — a GCP-native platform build, an AWS-to-GCP migration, and Azure cost governance — on one Terraform and Jenkins toolchain, with senior engineers accountable across all three.
Working constraints
- A live platform — no disruptive cutovers
- Three independent cloud environments
- An existing Terraform and Jenkins toolchain to build on
The transformation
Fragmented estate to governed platform
Before
- Fragmented cloud environments
- VM-heavy workloads
- Manual infrastructure changes
- Inconsistent monitoring
- Rising cloud costs
The engineering
- 1Terraform infrastructure foundations
- 2CI/CD automation on Jenkins
- 3EC2-to-GKE re-platforming
- 4IAM, monitoring and logging improvements
- 5Azure cost-governance framework
After
- Repeatable infrastructure
- More scalable, container-based workloads
- Stronger operational visibility
- Consistent delivery controls
- ~30% lower cost in the verified scope
Field notes on this class of problem
All field notesAWS to GCP: what actually changes (and when not to move)
A re-platforming exercise with a service-mapping problem — including the case for staying.
20 min read
Kubernetes & platformAutoscaling for traffic spikes: beyond a single HPA
Layer pod, node and event-driven scaling — a lone HPA won't survive launch day.
21 min read
FinOpsFinOps for DevOps teams: cost accountability without the blame
Make spend as observable as latency — visible, owned and continuously improved.
16 min read