tale of Theseus’s ship. A Better Way – The Strangler Pattern: Theseus’s activities fall into what the software world now calls the strangler pattern: a way to incrementally modernize a legacy system as Cheshire Cat.  The strangler pattern overcomes a critical problem many of us have faced in applying Agile techniques to modernizations. In the absence of the strangler pattern, we would develop a new system quickly and frequently. Legacy modernizations cannot be done in an Agile way without the strangler pattern.Coming up in Part Two Enterprise Architecture: Enterprise Architecture, the domain of the IT bureaucrats

actions, release becomes a business decisions, not a technical decision v. Environment-based Release Pattern – multiple environments available, only one is receiving live traffic. Release performed by moving moving traffic to the new environment, i.e. blue-green deployments vi. Application-based Release Pattern – modify application to selectively release functionality by small configuration changes. Feature iii. What works at scale 1X rarely works at scale 10X or 100X d. USE THE STRANGLER APPLICATION PATTERN TO SAFELY EVOLVE OUR ENTERPRISE ARCHITECTURE i. Coined by Martin Fowler in 2004 ii. Strangler

TECHNIQUES i. Anomaly detection is “the search for items or events which do not conform to an expected pattern.” ii. Smoothing – suitable for time series data. Using moving averages to reduce short-term fluctuations

avoid; continuously transforming and modernizing the company’s IT systems makes Fowler’s strangler pattern into an IT strategy rather than just a coding tactic. If you missed last month, you can find this