$ cat how-to-strangle-your-project-with-strangle-anti-pattern.md
How to Strangle your Project with Strangle Anti-Pattern
The article explains why the strangle pattern, a common approach to incrementally upgrading a codebase one section at a time, often backfires in practice. It describes how teams end up running two frameworks and doubling their complexity, and it introduces a better upgrade strategy to use instead.
Rector03 Mar 2025 · 1 min read · summary
Read on getrector.com ↗Nearly half of the projects we help upgrade have tried the upgrade before on their own.
They've introduced the infamous "strangle pattern". It's a way to upgrade a project separating one part of the codebase from the rest at a time.
Those companies reach us because while the strangle pattern is great in theory, it rather strangles the project in practice. They're unable to move, they use now 2 frameworks instead of one and the team has to work with complexity squared.
Today we'd like to share why it's a terrible choice and what upgrade strategy to take instead.
source
This is a summary of an article first published by Rector. The full piece is on their site.