IMS Saigon

The Strangler Fig Pattern: Modernize Without a Big-Bang Rewrite

Decompose legacy monoliths incrementally behind a reverse proxy routing layer with zero downtime.

  • strangler fig pattern modernization
  • monolith decomposition
  • YARP reverse proxy
The Risks

Why Big-Bang Rewrites Fail

Full rewrites carry a brutal risk profile:

Value Delay

Value arrives only at the end — often two years and several reorganizations later.

Moving Targets

The legacy system doesn't stand still. Every feature added during the rewrite must be built twice.

Hidden Rules

Hidden business rules live only in old code. A rewrite rediscovers them in production, as incidents.

The Cut-over Cliff

Cut-over is a cliff. One weekend, one switch, one company-wide bet.

The Architecture

How the Pattern Works

The strangler fig pattern inverts these risks: value ships from month two, features are built once, and there is never a cliff — only small, reversible steps. Three components make it run:

01

The Facade (Routing)

An API gateway or reverse proxy sits in front of everything. Clients never talk to legacy directly. Routing rules decide whether a request goes to legacy or new.

02

Capability Slices

You modernize by business capability (invoicing, pricing) — not by technical layer. Each slice is independently valuable and reversible.

03

Data Synchronization

During transition, the new service owns its data and changes are synchronized via change data capture or events so legacy keeps functioning.

Incremental Delivery

Reference Architecture

The Phases

The Playbook We Use

  1. 1Phase 0

    Seams and Safety (2–4 weeks)

    Install the facade with 100% traffic still going to legacy. Add observability to learn real usage: which endpoints, which volumes, which capabilities are actually alive.

  2. 2Phase 1

    First Slice (4–8 weeks)

    Pick a high-pain but low-entanglement capability. Build the new service, run it in shadow mode (both systems process, results compared), then dial traffic over.

  3. 3Phase 2

    Rhythm (Ongoing)

    One slice per iteration. Each slice funds the next through delivered value: faster feature delivery, retired licenses, reduced incident load.

  4. 4Phase N

    Retirement

    When routing shows 0% legacy traffic for a capability, its code is deleted. The monolith shrinks until switch-off is a non-event.

Modernize Without Betting the Company

Our architects have executed strangler migrations for enterprise clients where downtime was not an option. Book a modernization strategy session — we will identify your first slice and give you a risk-managed migration plan.

Book Strategy Session

Frequently asked questions

How long does strangler migration take compared to a rewrite?

Total duration is often similar — but value arrives from month two instead of year two, and risk per step is a fraction of a big-bang cut-over.

Does this lead to microservices automatically?

No, and it shouldn't. We extract services only where team autonomy or scaling justifies it; several slices can land in a single well-structured modern application ('modular monolith').

What is the most common mistake?

Slicing by technical layer ('migrate the database first') instead of business capability. Layer-slicing creates long periods with no user-visible value — the political death of the program.

More in .NET Modernization

.NET Modernization

.NET Modernization: From Legacy Framework to Cloud-Native .NET 8

Get In Touch

Let's Build Something Amazing

Ready to transform your ideas into reality? Fill out the form and our team will get back to you within 24 hours.