strangler fig
Replace an existing system incrementally by routing selected behavior to a new implementation.
Use this when A large rewrite needs smaller, reversible releases.
without the term
“I want to rewrite this old backend but I'm scared of doing it all at once. Can we move pieces over to the new code gradually and keep the old one running until each piece works?”
with the term · How do you ask a model for strangler fig?
Replace this endpoint using the strangler pattern. Preserve its contract, verify the selected path, and document cutover and rollback.
What is strangler fig?
New code takes over one route or feature at a time, behind a switch, while the old system keeps serving everything else. The old path is deleted only after its replacement is proven.
Why does strangler fig matter when vibe coding?
A rewrite can drop edge cases hidden in the existing system.
How do you do strangler fig?
Move one boundary at a time, compare behavior, and define when the old path will be removed.
What goes wrong with strangler fig?
Keeping two implementations indefinitely with no owner for their divergence.