Legacy modernisation without a big-bang rewrite
Strangler-fig patterns let you replace a legacy system incrementally, with value delivered every few weeks.
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
- Put a thin routing layer in front of the legacy system
- Rebuild one vertical slice in the new stack
- Route only that slice to the new code
- 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
The case against a microservices-first architecture
For most teams under fifty engineers, a well-structured monolith ships faster and costs less. Here is where we draw the line.
Read articleSecuring file uploads in a CMS
CVs, artwork and documents are the most commonly exploited part of any content-managed site. A practical checklist.
Read articleWhat 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