0% completed
The Strangler Pattern: A Solution
Implementation starts by choosing one piece of the legacy system that can be rebuilt on its own. A good first choice has a clear boundary and low risk, such as a page that only reads data.
That piece is built in the new system. A facade is a single entry point that hides what is behind it. It receives every request and decides which system handles it. Requests for the rebuilt piece go to the new system. Everything else goes to the old one. Over time more pieces move, and traffic to the legacy system falls until none is left.
The four steps
- Identify a piece to move: pick a part of the legacy system with a clear boundary.
- Route the traffic: put a facade or proxy in front, so the choice of system is one decision in one place.
- Rebuild and replace, piece by piece: each piece is built, routed and watched before the next one starts.
- Retire the old system: when nothing routes to it, switch it off and remove it.
This order matters. The facade goes in before the first piece is migrated, not after it. Without it there is no way to move traffic gradually, and the migration becomes the single large cutover the pattern exists to avoid.
prabal kene
· 2 years ago
Is there a video classes available for this course Microservices Patterns.
Reading Progress
0%