Skip to content
MEDIA IT SOFT
Engineering 3 min read

Legacy modernisation without a big-bang rewrite

Strangler-fig patterns let you replace a legacy system incrementally, with value delivered every few weeks.

JW By James Whitfield
Legacy modernisation without a big-bang rewrite

Full rewrites fail predictably: the business changes underneath you while the new system is invisible. We prefer to strangle the old system one capability at a time.

How it works in practice

  1. Put a thin routing layer in front of the legacy system
  2. Rebuild one vertical slice in the new stack
  3. Route only that slice to the new code
  4. Repeat, measuring each migration

The legacy system keeps earning while it shrinks, and every milestone is a working release rather than a status update.

Related articles

Engineering 3 min read

Securing file uploads in a CMS

CVs, artwork and documents are the most commonly exploited part of any content-managed site. A practical checklist.

Read article
Engineering 3 min read

What we look for when hiring engineers

Not leetcode. We care about how you reason about trade-offs, communicate uncertainty and handle being wrong.

Read article

Ready to build something exceptional?

Tell us about your project and we will come back with a clear plan.