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

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