eCommerce Modernization
Scaling digital commerce with MACH architecture.
- Period
- 2021–2024
- Role
- Technical leadership
- Context
- Retail eCommerce platform migration
- Outcome
- Delivered platform modernization with ongoing operational service
A large retail commerce platform needed to evolve from a tightly coupled system towards more replaceable capabilities without disrupting live operations.
Situation
The commerce estate had grown around a monolithic platform that made changes slow and risky. Each feature addition or supplier change required coordination across the entire stack. The business needed faster iteration, but the cost of a wholesale rewrite was prohibitive and the operational risk unacceptable.
Problem
The central challenge was finding a migration path that improved the ability to change without pretending that a new architecture removed all operational complexity. Every architectural decision had to be weighed against delivery continuity, migration cost and the capacity of existing teams.
Constraints
Migration risk, delivery capacity, budget and continuity for existing commerce operations shaped every decision. The platform had to remain fully operational throughout the transition, with no acceptable downtime window for a cutover.
My remit
I worked on the technical and product decisions guiding the transition, balancing the pace of change against operational stability. This included evaluating architecture options, defining service boundaries and establishing the sequencing of the migration.
Key decisions
The approach favoured clear service boundaries and incremental replacement over a platform rewrite. We identified capabilities that could be extracted independently and migrated one at a time, retiring the corresponding monolithic code paths as each replacement went live. Deliberately not done: a lift-and-shift to a new platform without rethinking the service boundaries first.
Outcome
The work established a more deliberate route towards a cloud-native architecture with replaceable commerce capabilities. The platform remained operational throughout the migration, and each extracted service reduced the coordination surface area for subsequent changes.
Lessons
Architecture is useful when it makes the next safe change easier, not when it merely changes the diagram. Incremental migration preserves operational knowledge that a rewrite discards.
