Strangler Pattern for Monolithic to Microservices migration

Описание к видео Strangler Pattern for Monolithic to Microservices migration

Strangler Pattern: Majority of the current applications are legacy monolithic applications, which can’t be decomposed in microservices in a single attempt. It takes a long time to migrate all monolithic applications into microservices, which can be done in phase-wise. Modern cloud native applications follow the Agile development approach, where they are deployed in phase-wise sprints in non-production and production. In this design pattern, a monolithic app can be broken into smaller business domains in phase-wise. In this phase-wise approach, first an independent low business critical service can be extracted from a monolithic app as a microservice and deployed on production, where client applications access the newly extracted microservice and old monolithic apps both. Other business services of a monolithic app can be extracted to microservices to cloud after successfully testing phase-wise. In this approach, the monolithic app and extracted microservices both are deployed on production at the same time. The client call goes to both until all services of the monolithic application can be extracted to microservices and deployed on production. When all monolithic applications are extracted to microservices, then the monolithic app will be retired at the end. The strangler design pattern is best suited for migration from legacy monolithic applications to microservices.

The advantages are as follows:
It’s good for web applications. It’s a safe and easy way to migrate monolithic apps to modern microservices in phase-wise.

Limitations The limitations are as follows:

This process takes time to fully migrate monolithic apps to microservices. Sometimes, it takes a couple of months to years. This is complex to manage, test, and debug because business logics are spread across both microservices and monolithic applications.

Use cases:

Migrate a big legacy app to microservices which contains many business logics.
If an organization wants to move to the cloud phase-wise to avoid any kind of risks.
monolith to microservices,monolith to microservices migration,monolith to microservices migration patterns,breaking monolith to microservices,decomposing monolith to microservices,monolith to microservices interview questions,microservices architecture patterns,microservices architecture, strangler pattern

Welcome: (0:00)
Advantages of Monolith to Microservices migration : (0:04)
Risk Involved: (1:28)
Strangler Pattern Explained: (1:54)
Advantage / Disadvantage / Use Case: (4:18)
Thank You: (4:46)

Комментарии

Информация по комментариям в разработке