Skip to content
How to Upgrade Old Software Without Stopping Your Business

How to Upgrade Old Software Without Stopping Your Business

Balaji Naidu avatarBalaji Naidu13 min read

In short

  • The traditional 'Big Bang' rewrite—where you build a completely new system in parallel and try to switch over overnight—is the riskiest IT maneuver an enterprise can attempt.
  • The Strangler Fig Pattern works by placing an API Gateway in front of the legacy system, then rebuilding individual features one by one as modern microservices.
  • This approach delivers ROI early and often, reduces deployment risk, and allows the business to continue operating smoothly during the transition.

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.

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.

Want this done for you? WebMarv offers software modernization, backend & cloud development and software maintenance & support. Start with a free audit.

  • Architecture
  • Legacy Modernisation
  • Enterprise Tech
  • Engineering
Balaji Naidu - Founder & Growth Engineer

Written by

Balaji Naidu

Founder & Growth Engineer

Balaji Naidu is the founder of WebMarv Innovations LLP. He connects business growth with digital systems — from search visibility and demand generation to conversion funnels and revenue attribution. He leads strategy, growth engineering, and business development.

  • Marketing & SEO
  • System Architecture
  • Next.js
  • Revenue Systems
  • Business Strategy
View founder profile & articles →

FAQ

Questions about this topic

Not answered here? Ask us directly.

Why is it called the Strangler Fig Pattern?

The name comes from the strangler fig tree, which seeds in the upper branches of a host tree and gradually grows roots down to the ground. Over time, it completely envelops and replaces the host tree. In software, new microservices gradually wrap around and replace the old monolith.

Why not just rewrite the whole system from scratch?

Because it takes years. While your team is spending 3 years rebuilding the old system, your competitors are adding new features. Furthermore, 'Big Bang' switch-overs are notoriously risky and often result in catastrophic data loss or downtime.

How does the user know which system they are using?

They don't. We place an API Gateway (a traffic router) in front of everything. When a user requests a modernized feature (like 'Billing'), the gateway routes them to the new microservice. For all other requests, it routes them to the legacy system. The transition is invisible to the end user.

What happens to the legacy database?

Data migration is the hardest part. Typically, the new microservice gets its own modern database. We set up synchronization mechanisms (like event streaming with Kafka) to keep the old and new databases in sync until the legacy system is fully decommissioned.

WebMarv background pattern

Free audit

Want this done for you? Free audit.

“Families traveling from rural districts can now read about conditions in Telugu before visiting Kurnool, and booking an appointment on their phone is effortless. WebMarv's engineering gave our practice a digital foundation we can trust.”

Dr. Swetha Rampally·Consultant Pediatric Neurologist, Dr. Rampally's Child Neuro Care

Case study ↗
Step 1 of 4
Which solution do you need?
Tap an option to continue