gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Files
6fe219d644bb9f80c4190c82b1a45eb91089bc88
java-design-patterns/strangler
History
ZhouSky 6fe219d644 Pr/1235 Review (#1250) 
* Add simple implementation for strangler pattern.

* Add strangler pattern in pom.xml.

* change package name

* Revert "change package name"

This reverts commit 430bd9073e.

* Code review for strangler

Delete final of method parameters.
Add final to private members.
Change package name.

* Revert "Code review for strangler"

This reverts commit d506356708.

* Revert "Revert "Code review for strangler""

This reverts commit c8fd65fda7.

* Remove unnecessary files
2020-07-04 12:05:46 +03:00
..
etc
Pr/1235 Review (#1250)
2020-07-04 12:05:46 +03:00
src
Pr/1235 Review (#1250)
2020-07-04 12:05:46 +03:00
pom.xml
Pr/1235 Review (#1250)
2020-07-04 12:05:46 +03:00
README.md
Pr/1235 Review (#1250)
2020-07-04 12:05:46 +03:00

README.md

layout, title, folder, permalink, categories, tags
layout title folder permalink categories tags
pattern Strangler strangler /patterns/strangler/ Structural
Extensibility

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

alt text

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.

Credits