Every enterprise has one. The "Core System." It is a massive, monolithic application written 15 years ago. It runs the entire business.
It is also a nightmare. It takes three days to deploy a minor text change. The code is a tangled mess of spaghetti. The original developers left five years ago. Nobody knows exactly how the billing module works, so everybody is terrified to touch it.
Eventually, the CTO decides enough is enough. "We need to rewrite this in modern technology."
This usually leads to the most dangerous maneuver in enterprise IT: The "Big Bang" Rewrite.
The Trap of the Big Bang Rewrite
The plan sounds logical: Leave the old system running. Build a brand new, perfect system in parallel. When the new one is finished, flip the switch on a weekend and turn off the old one.
Industry data shows these projects have a failure rate approaching 70%. They run millions over budget, take three times longer than estimated, and when the switch is flipped, critical undocumented business logic from the old system is inevitably missed, bringing operations to a halt.
There is a better, safer engineering approach: The Strangler Fig Pattern.
How the Strangler Fig Pattern Works
Instead of rewriting the entire monolith at once, you systematically replace it one piece at a time, while the system is still running.
Step 1: The API Gateway Interceptor
We do not touch the legacy code yet. First, we place a new "API Gateway" (a smart traffic router) in front of the legacy system. All user traffic now hits the gateway, which simply passes every request straight through to the old monolith. Nothing has changed for the user.
Step 2: Extract a Single Service
We pick one specific, manageable feature—for example, the User Authentication module. We build a brand new, modern microservice specifically for authentication. We thoroughly test it.
Step 3: Route the Traffic
We tell the API Gateway: "If a request is for 'Authentication', route it to our new microservice. If the request is for anything else, send it to the legacy monolith."
Instantly, the authentication feature is modernized. The user experiences zero downtime. If something goes wrong, we just change the router rule back to the old system in seconds.
Step 4: Strangle the Monolith
We repeat this process. We extract the "Billing" module. Then the "Inventory" module. Over months or years, more and more traffic is routed to the new microservices.
Eventually, the legacy monolith is handling zero traffic. It has been completely "strangled" by the new modern architecture. You can now safely turn it off forever.
The Engineering ROI
The Strangler Fig pattern requires discipline and careful data management, but it is the only responsible way to modernize mission-critical enterprise systems.
- Zero Downtime: Deployments are small and isolated.
- Continuous Value: You don't wait three years to see ROI. The business gets a faster, better Authentication module in month one.
- Minimal Risk: You are never betting the entire company on a single weekend switch-over.
Legacy modernisation isn't about being bold. It is about being surgical.
