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

Using of global variables in C# - Drawbacks & Solutions

How using global variables can have implications on the design, maintainability, and test-ability of C# code: Harder to understand and reason about the code:       class Program     {         public static int globalCounter = 0;         static void Main()         {             globalCounter++;             Console.WriteLine(globalCounter);         }     }   In this example, the global variable globalCounter is accessible from anywhere in the program, including the Main method. It's not clear where the value of the globalCounter is updated, it could be updated in other methods or classes, making it harder to trace the flow of data and understand the source of bugs.   More prone to errors:       class Program     {         public static string globalString;         static void Main()         {             globalString = "Hello" ;             Method1();             Method2();         }         static void Method1()         {
Post a Comment
Read more

Task Parallel Library (TPL) and Akka.NET Alternatives

Task Parallel Library (TPL) and Akka.NET are among the most commonly used libraries for parallel and concurrent programming in the .NET ecosystem. However, there are also several other options available, depending on your specific needs: Parallel Language Integrated Query (PLINQ) is a parallel programming feature of .NET that provides an easy and efficient way to perform operations on collections in parallel. LINQ (Language Integrated Query) is a powerful feature in .NET that allows developers to work with data in a more declarative and language-integrated manner. While LINQ queries are inherently sequential, PLINQ extends LINQ by providing parallel versions of the query operators, allowing some queries to execute faster by utilizing multiple processors or cores on a machine. PLINQ is great when you are working with large collections where operations might be CPU-intensive or I/O-bound and could potentially be sped up by parallel execution. Here is a simple example of a PLI
Post a Comment
Read more

SOLID Principles with Real World examples in C#

  SOLID Principles with Real World examples in C#   SOLID principles are formed by using S Single Responsibility Principles (SRP) O Open Closed Principle (OCP) L Liskov’s Substitution Principle (LCP) I Interface Segregation Principle (ISP) D Dependency Inversion Principle (DIP)   S Single Responsibility Principles (SRP) There should never be more than one reason for a class to change, to be precise one class should have only one responsibility Single Responsibility Principles (SRP) Real world example, A perfect match for SRP is Microservices , a Microservice will not contain functionalities other than the one it is designated to do,  Example ·                   Order Processing Service, ·                   Shipment Management Service, ·                   User Authentication Service, ·                   Catalogue List Service       class OrderProcessor     {         public void Process(Order order)         {             // Check inven
Post a Comment
Read more