A full rewrite concentrates risk into a large release and often discovers undocumented behavior too late. The Strangler Fig pattern replaces a legacy system capability by capability.
Find a safe seam
Identify a route, workflow, or domain capability that can be separated from the old implementation. Introduce a routing boundary that can direct selected requests to the new component while the rest continue using the legacy path.
Preserve behavior first
Document current behavior, including edge cases and integrations. Use characterization tests and representative production observations where appropriate. The first replacement should match required behavior before attempting broad redesign.
Manage data ownership
The hardest part is often shared data. Define which system is authoritative for each record and how synchronization works during transition. Avoid two systems independently writing the same fields without conflict rules.
Retire deliberately
Measure traffic to the old path, remove unused integrations, and preserve rollback options until the new capability is proven. Do not allow the transitional routing layer to become permanent undocumented complexity.
Checklist
- Choose a capability with a clear boundary.
- Capture existing behavior before replacement.
- Define one authoritative owner for each data set.
- Route traffic incrementally with rollback.
- Remove the legacy path after evidence supports retirement.