A ten-year-old PHP monolith's checkout flow was the highest-risk, highest-traffic part of the codebase, and a full rewrite was too risky to attempt in one cutover. We used a strangler-fig approach — routing traffic incrementally to a new implementation behind a feature flag — to replace it in six weeks with zero downtime.
Route by percentage, not by big-bang cutover
Instead of a single cutover date, we shipped the new checkout path behind a flag and shifted traffic in small increments — 1%, then 5%, then 25% — comparing conversion, latency, and error rate against the legacy path at every step. Any regression rolled back to 0% instantly with no deploy required.
Instrument before you migrate, not after
The legacy checkout had almost no structured logging. Before writing a single line of the replacement, we instrumented the old path with the same metrics we'd need to validate the new one — this turned "does the new checkout work?" from a guess into a side-by-side comparison with real numbers.
- Instrument the legacy system with the metrics you'll need to validate the replacement
- Ship the new path behind a flag before it handles any real traffic
- Shift traffic in small percentage increments with an instant rollback
- Decommission the legacy path only after the new one has carried 100% of traffic under real load for a full billing cycle
What is the strangler-fig pattern in legacy modernization?
It's an incremental migration strategy where a new implementation is routed a growing percentage of production traffic behind a feature flag, while the legacy system keeps running, until the new system has proven itself and the old one is safely retired.
How do you modernize a critical system without downtime?
Instrument the legacy system first, ship the replacement behind a flag, shift traffic incrementally while comparing metrics side by side, and keep an instant rollback path until the new system has carried full production load reliably.
Hayden Jackson
Get engineering notes in your inbox
Practical AI, cloud, and security delivery notes - no fluff, no sales spam.