Skip to main content

What is Microservices Strangler pattern - Uses and Steps

The Strangler pattern is a technique used to gradually migrate a monolithic application to a Microservices-based architecture. It involves creating new services to replace specific functionalities of the monolithic application, while leaving the rest of the application intact. The new services are gradually "strangled" around the existing monolithic codebase, until the entire application is replaced by a set of Microservices.

Steps to implement the Strangler pattern with Microservices:

    Identify the functionalities of the monolithic application that are good candidates for migration to Microservices. These are typically functionalities that are tightly coupled to a specific subset of the application's data and have a clear, well-defined set of inputs and outputs.

    Create new Microservices to replace the identified functionalities. These Microservices should be loosely coupled to the rest of the application and have a clear, well-defined API.

    Decouple the new Microservices from the monolithic application by creating an API gateway or a reverse proxy that routes incoming requests to the appropriate service.

    Gradually replace the monolithic code with calls to the new Microservices. This can be done by creating new endpoints in the monolithic application that invoke the corresponding Microservices.

    Monitor the performance of the new Microservices and the monolithic application to ensure that the migration is not causing any negative impact.

    Repeat the process of identifying functionalities, creating new Microservices, and replacing the monolithic code until the entire application has been migrated to a Microservices-based architecture.

 Strangler pattern is a gradual process that can take a long time to complete, depending on the size and complexity of the monolithic application.

Labels:

Comments

Post a Comment

Popular posts from this blog

Task Parallel Library (TPL) and Akka.NET: Differences

Task Parallel Library (TPL) and Akka.NET are both powerful tools in the .NET ecosystem for handling parallelism and concurrency, but they serve different purposes and use different models of computation. Here are some key differences:s 1.    Actor Model vs Task-Based Model: Akka.NET is built around the actor model, where actors are the fundamental units of computation and they communicate by exchanging messages. TPL, on the other hand, is task-based. It's designed to make developers more productive by simplifying the process of adding parallelism and concurrency to applications. TPL uses tasks (which are independently executing work units) and provides various ways to control and coordinate them. 2.    Fault Tolerance: One of the key features of Akka.NET is its built-in fault tolerance. It has a "let-it-crash" philosophy, where the system is designed to self-heal from errors. If an actor fails, its parent actor can decide on the supervision strategy: either to resta
Post a Comment
Read more

Extension Methods - Advanced

Here we will see how can we use the Extension Methods in advanced manner in other types Imagine you often need to retrieve items from a List based on a custom criterion that the built-in LINQ methods don't cover. Extension Methods for Lists: Filtering based on Custom Criteria And the output would be   Extending Enums: Displaying Descriptive Strings Output: Extending DateTime: Calculating Age     Output: The code samples can be found at https://github.com/oneananda/C_Sharp_Examples/tree/main/ExtensionMethods
Post a Comment
Read more