StranglerFigApplication

StranglerFigApplication

8/19/2021

link

https://martinfowler.com/bliki/StranglerFigApplication.html

summary

In this blog post, Martin Fowler introduces the concept of the "Strangler Fig Application" as a strategy for modernizing legacy systems. The term "strangler fig" is derived from a type of tree that grows around an existing tree, eventually strangling and replacing it. Similarly, the Strangler Fig Application approach involves gradually replacing components of a legacy system with new, modernized ones. Fowler explains the benefits of this approach, such as reducing risk and allowing for incremental change. He also discusses the challenges and considerations that arise when implementing a Strangler Fig Application, emphasizing the importance of a well-defined boundary between the old and new components. Overall, the article provides insights into a useful strategy for modernizing and refactoring legacy systems.

tags

software architecture ꞏ code refactoring ꞏ legacy systems ꞏ application modernization ꞏ monolithic architecture ꞏ microservices ꞏ software design ꞏ application migration ꞏ system decomposition ꞏ software development ꞏ architecture patterns ꞏ software engineering ꞏ software transformation ꞏ system integration ꞏ software evolution ꞏ software maintenance ꞏ code base ꞏ software complexity ꞏ software scalability ꞏ code quality ꞏ system architecture ꞏ code structure ꞏ software modularity ꞏ software deployment ꞏ code reuse ꞏ system resilience ꞏ software agility ꞏ software flexibility ꞏ code maintenance ꞏ software testing ꞏ software documentation ꞏ software patterns ꞏ software assets ꞏ software sustainability ꞏ software stability ꞏ system stability ꞏ software extensibility ꞏ software reliability ꞏ system reliability ꞏ software performance ꞏ system performance ꞏ software dependencies ꞏ system dependencies ꞏ software architecture principles ꞏ software architecture styles ꞏ software architecture patterns ꞏ software architecture best practices ꞏ code analysis ꞏ software metrics