Retail & E-commerce
Replatforming a multi-market commerce operation
A retailer running twelve markets on a single monolith could no longer launch a country without a release freeze.
- faster response times
- 70%faster response times
- traffic capacity
- 3xtraffic capacity
- lower infrastructure cost
- 40%lower infrastructure cost
The Challenge
The business had grown from three markets to twelve on a platform designed for one. Every market launch required coordinated downtime, and peak-season traffic was handled by over-provisioning the entire stack for the whole year.
The Problem
A single deployable coupled catalog, pricing, content and checkout across all markets. Cache invalidation was global, so a price change in one country cleared the cache for every other. Response times degraded non-linearly above 40,000 concurrent sessions.
Our Approach
We moved to a headless architecture with commercetools as the commerce engine and a Next.js storefront served from the edge. Market configuration became data rather than code, and cache keys were scoped per market. We migrated market by market, running old and new in parallel behind a routing layer so no launch required a freeze.
Technology
- commercetools
- Next.js
- TypeScript
- Akamai
- Redis
- Kubernetes
- AWS
The Result
- faster response times
- 70%
- traffic capacity
- 3x
- lower infrastructure cost
- 40%
Impact matters more than technology.
Have a complex problem? Let’s talk.
Whether you’re building something new, modernizing an existing platform or trying to solve a problem that doesn’t have an obvious answer, we’d like to hear about it.