StranglerApplication

4/27/2019

In this blog post, Martin Fowler introduces the concept of the "Strangler Application" as a strategy for modernizing complex software systems. The Strangler Application approach involves gradually replacing components of a legacy system with new, modern components over time. This approach allows for iterative improvements and reduces the risk of disrupting the entire system during the transition process. Fowler discusses the benefits and challenges of this approach, highlighting the importance of identifying boundaries within the legacy system and gradually strangling it by adding new functionality and eventually decommissioning the old components. Overall, the Strangler Application pattern provides a practical way to evolve and modernize large, monolithic software systems.

strangler application ꞏ monolithic architecture ꞏ microservices ꞏ software refactor ꞏ software modernization ꞏ software evolution ꞏ legacy system ꞏ software architecture ꞏ software design ꞏ codebase ꞏ codebase refactoring ꞏ software maintenance ꞏ software development ꞏ software engineering ꞏ software patterns ꞏ code decomposition ꞏ system decomposition ꞏ code migration ꞏ system migration ꞏ software complexity ꞏ software scalability ꞏ software reliability ꞏ software flexibility ꞏ software performance ꞏ software agility ꞏ software modularity ꞏ software decoupling ꞏ software testing ꞏ software deployment ꞏ software integration ꞏ software upgrade ꞏ software transformation ꞏ software reuse ꞏ software architecture patterns ꞏ software development practices ꞏ software development methodology ꞏ software development lifecycle ꞏ software quality ꞏ software metrics ꞏ code readability ꞏ code maintainability ꞏ code consistency ꞏ code reusability ꞏ code efficiency ꞏ code optimization ꞏ code organization ꞏ code review