Ace8 is the modernization practice of AceMQ.24/7 support from AceMQ after go-live
Book an Assessment

Guide

The strangler fig pattern: replace a system without stopping it.

Put a facade in front of the old system. Move one capability at a time behind it. Retire the old parts when nothing uses them.

AceMQ engineering team3 min readEngineer-reviewed

How traffic movesPick a phase to see where requests go.

Phase 2 · ShiftOne capability now runs on new code. Send it a small share, compare results, widen. Switch back any time.

The short answer

The strangler fig pattern replaces a legacy system gradually. You place a facade or proxy in front of it, build new functionality behind that facade one capability at a time, route traffic to the new code in steps, and retire the old parts when nothing calls them. The system stays live throughout, and each step is small enough to reverse.

Stacks we work in

  • RabbitMQ
  • Java
  • Spring Boot
  • Kubernetes
  • PostgreSQL
  • Kafka
  • Docker
  • Terraform
  • GitHub Actions
  • RabbitMQ
  • Java
  • Spring Boot
  • Kubernetes
  • PostgreSQL
  • Kafka
  • Docker
  • Terraform
  • GitHub Actions

Origin

Where does the name come from?

Martin Fowler described the pattern in 2004, after strangler figs he saw in Australian rainforests. The vine grows around a host tree, eventually replaces it, and the tree dies. Fowler's point was that rewriting a system in one go is risky, and growing a replacement around the old system is safer.

The idea is also called incremental modernization. Our method uses it as principle 3, 'Strangle, don't big-bang'.

Mechanism

How does the facade work?

The facade is a layer in front of the old system that receives every request. It decides, per request, whether the old or the new implementation handles it. For a web application that is usually a reverse proxy, API gateway or routing rule. For messaging or batch work it can be an adapter or a routing component.

The facade does three jobs. It gives callers one stable interface, so they do not notice the change. It lets you switch a capability from old to new without changing the callers. And it lets you switch back, because the old path is still there until you remove it.

Planning this for your estate? Get a fixed scope and price first.

Sequence

The steps, in order

Step 01 of 06

Pick a capability

Choose a slice with clear boundaries and low coupling, such as one report, one endpoint or one queue.

Applied

A phased broker migration

American National, an insurer, moved from IBM MQ to RabbitMQ in phases, with the AceMQ engineering team refactoring the legacy code that depended on the old broker. The migration had no big-bang cutover. See the American National case study.

This is the same shape as the steps above, applied to a messaging layer instead of a web endpoint. Each phase moved a portion of the work, was reviewed before the next, and stayed reversible. The project was delivered by the AceMQ engineering team.

Limits

When not to use it

In these cases consider a contained rewrite, a lift and shift first, or a different order. The assessment checks for these conditions.

Senior engineer reviewChecked by hand before anything merges5 checks
  • F-01The system is small and a rewrite takes weeks. The facade costs more than it saves.
  • F-02There is no seam to intercept: no network boundary, API or interface where you can place the facade.
  • F-03A shared database that cannot be split. Old and new code writing the same tables creates data conflicts you must plan for.
  • F-04The old system will be switched off by a fixed date, such as a contract end, that leaves no time for phases.
  • F-05No tests and no way to compare old and new results. You cannot tell if a shifted slice behaves the same.

Pitfalls

What goes wrong in practice

Senior engineer reviewChecked by hand before anything merges4 checks
  • F-01The old system never gets retired, and you run both indefinitely. Put a retirement date on every slice.
  • F-02The facade becomes a new monolith of routing rules. Keep it thin.
  • F-03Slices chosen by org chart rather than by coupling, so each one drags dependencies with it.
  • F-04Data left out of the plan. Decide per slice which side owns the data and how it syncs.

Next step

How Ace8 helps

Ace8 is the AI-assisted application modernization practice of AceMQ. Our 8 principles put 'Strangle, don't big-bang' third, and our assessment produces the phase plan: a list of capabilities, their interfaces and the traffic-shift steps. Start with the modernization assessment to find the first slice.

FAQ

Frequently asked questions

Something else on your mind? Ask an engineer.

A way to replace a legacy system gradually by routing requests through a facade and moving capabilities to new code one at a time.

Start here

Know the cost before anything moves.

A fixed-price assessment gives you the inventory, the risk score and a phased plan. Scope and cost are fixed before the migration starts.

  • InventoryEvery application, its stack and what it depends on.
  • Risk scoreWhere a change is likely to break, ranked.
  • Phased planWhat moves first, which tools lead, and the fixed price.

Get in touch

Talk to a modernization engineer

Tell us what you run today. An engineer, not a sales script, replies within one business day.

305-204-2607info@ace8.io

66 W. Flagler St. 9th Floor
Miami, FL 33130

What are you moving off? *

Fixed price. Scope and cost before any migration starts.