The new system grows next to the old one until the old one can go
Traffic to the old system passes through a layer that routes feature after feature to new modules. Every release shrinks the old system, and you have a working product at every stage.
Four steps of the rebuild
Shown on an order system.
- 1A layer in frontWe put a layer in front of the old system that every request passes through. At first it simply passes them on.
- 2First moduleWe build a new version of one feature, such as placing orders, and route traffic to it.
- 3More modulesModule by module, traffic moves to new code. The old module stays on standby until the new one proves itself.
- 4Old system switched offWhen nothing goes through the old part any more, we switch it off and remove the transition layer.
Signs this approach is for you
A full rewrite is too risky
The last attempt failed
Part of the system is fine
Budget comes quarter by quarter
What we build the new modules with
We choose the technology to suit the team that will maintain the system.
Routing layer
Backend
Frontend
Data
Older interfaces
Deployments
How we track progress
After every release we check how many features have moved to new code and whether anything got worse.
- 1Features served by new code
- 2Traffic still going through the old system
- 3Bugs after a module switch
- 4Rolled-back releases
You see progress in a weekly demo, not in a report at the end of the project.
Common questions
Why "strangler"?
After the strangler fig, which grows around a tree until it replaces it. The new system grows around the old one the same way.
Doesn't it take longer than a rewrite?
Overall it can take about as long, but new code reaches production from the first phases rather than at the very end.
What if a new module performs worse?
One switch sends traffic back to the old module while we fix the new one.
Does all the data have to move at once?
No. During the transition old and new modules can share a database or sync data.
Describe the system to rebuild
Tell us what the system does, what it runs on and which parts cause the most trouble. We reply within one business day.