Definition
The Strangler Fig Pattern is an incremental approach to replacing a legacy system, in which new components are built alongside the old one and requests are routed to them piece by piece until the legacy system can be switched off.
Importance
Big-bang replacements of business-critical systems carry concentrated risk: years of work land in one release, and existing behavior usually proves harder to specify than expected. The strangler fig pattern spreads that risk out. Each slice of functionality goes live on its own, users see improvements early, and if a new component misbehaves, requests can be routed back to the legacy code. It also lets an organization pause the program at a sensible point if priorities change, without leaving a half-built replacement that delivers nothing.
Application
The pattern works by placing a routing layer, often an API gateway or proxy, in front of the legacy application. The team picks a well-bounded capability, builds its replacement, redirects the relevant requests, and retires that piece of old code once the new version is proven. We use the pattern in our Rearchitecting and Rebuilding work where the system suits it, typically a monolith that can't be taken offline, and choose a different path where it doesn't. Legacy and modern components run side by side during the transition, and each change is validated against production traffic before we retire the legacy code. Every slice has its own rollback plan, so a problem in one component never puts the whole system at risk.
Legacy App Modernization Services
Don't let legacy systems cap your growth.
From rehosting to full rebuilds, we modernize aging applications into secure, scalable platforms — freeing budget and engineering capacity that legacy systems consume.

