* Add simple implementation for strangler pattern. * Add strangler pattern in pom.xml. * change package name * Revert "change package name" This reverts commit430bd9073e
. * Code review for strangler Delete final of method parameters. Add final to private members. Change package name. * Revert "Code review for strangler" This reverts commitd506356708
. * Revert "Revert "Code review for strangler"" This reverts commitc8fd65fda7
. * Remove unnecessary files
layout, title, folder, permalink, categories, tags
layout | title | folder | permalink | categories | tags | |
---|---|---|---|---|---|---|
pattern | Strangler | strangler | /patterns/strangler/ | Structural |
|
Intent
Incrementally migrate a legacy system by gradually replacing specific pieces of functionality with new applications and services. As features from the legacy system are replaced, the new system eventually covers all the old system's features and may has its own new features, then strangling the old system and allowing you to decommission it.
Class diagram
Applicability
This strangler pattern is a safe way to phase one thing out for something better, cheaper, or more expandable. Especially when you want to update legacy system with new techniques and need continuously develop new features at the same time. Note that this pattern indeed need extra effort, so usually use it when the system is not so simple.