A strangler-fig migration off a monolithic commerce platform, absorbing 20× peak load with a single inventory truth.
Where it started
Store, web and marketplace channels each held their own view of stock, so oversells at peak were routine and reconciliation was manual. The commerce monolith could not be scaled independently, and the previous peak season had degraded badly under load with no way to shed traffic gracefully.
- 01
Placed a routing facade in front of the monolith and moved capabilities out slice by slice, each independently reversible.
- 02
Built an inventory service as the single source of truth, with event-driven reservation and compensation instead of channel-local counts.
- 03
Load-tested against twenty times normal traffic before peak, with a rehearsed degradation path that sheds non-essential features first.
- 04
Added demand forecasting to drive allocation, replacing a set of spreadsheets maintained by one person.
- Next.js
- Go
- Kafka
- Kubernetes
- Terraform
- GCP
Where it landed
Peak season ran without degradation at twenty times baseline load. Oversells fell by ninety-four percent once inventory had a single owner, and the remaining monolith now handles only back-office functions scheduled for retirement.
A short conversation with an engineer, not a sales qualification call. If we're the wrong people for it, we'll say so and point you somewhere better.