Monolith Modernization with APIs and Microservices: What is the Strangler Pattern and how to use it?
Many organizations have large integrated code-bases than often are referred to as "monoliths". All of these code-bases have in common that they are complicated, are hard to change, and are hard to deploy. This is not a good match for a world that's changing at an increasing pace, and organizations that have to keep up with this change.
Microservices are one popular alternative implementation model with small standalone implementations of well-defined capabilities, where these implementations can be changed and deployed independent of each other. Interactions only happen through the API of a microservice, which avoids coupling through more traditional implementation patterns such as shared libraries or databases.
When moving from a monolith to a more modern IT structure, one possible pattern is the "Strangler Pattern". It is based on strategically carving out capabilities out of the monolith, and implementing them as microservices. In this video, we take a closer look at this pattern and present a structured process of 13 steps that allows you to better understand how the strangler pattern works in practice.
00:00 Introduction
00:50 Introduction to the Strangler Pattern
01:31 Why Modernization?
01:51 Bottom-up: Service Scalability
03:12 Top-down: Digital Transformation
05:00 Typical Modernization Drivers
06:48 The Strangler Pattern for Modernization
08:00 Step 1: Motivate
08:31 Step 2: Identify
09:04 Step 3: Delineate
09:33 Step 4: Analyze
10:36 Step 5: Expose
11:14 Step 6: Manage
12:02 Step 7: Re-Implement
12:31 Step 8: Imitate
12:54 Step 9: Replicate
14:06 Step 10: Motivate
15:10 Step 11: Deprecate
15:40 Step 12: Retire
16:15 Step 13: Repeat
17:02 Conclusions