Skip to main content

Monolith vs Microservices - 1

Today we are going to see about the Monolith services vs Micro services and what are the key differences between them , advantages over one another, and finally specific purpose for each one.

Monolith Services: 

In simple terms, Monolith services are widely used technology in current software world, a traditional monolith service essentially runs in a single platform, a single stack which holds all the business logic and data access logic placed in a single service, also in most cases the UI, Business Logic and Data access layers are tightly coupled and deployed in a single machine, this may be available to scale but this is strictly stick to its own stack / platform

Advantages of Monolith: 

We can really get a lot of advantages for using Monolith services,

* Single code base (This is an advantage until the code base isn't growing enormously)

* No need to talk to other internal services to do a particular task as everything is available within

* Single stack / platform is needed for the whole team, in this case support gets easy  

* We can choose between the choices of "Tightly Coupled Monolith" and "Loosely coupled Monolith", this means the project can choose to deploy the services which consists of Business Logic and Data Access Layer in the same box where the UI is located or out of the box where the UI is located, in case of out of box then the services can talk to any eligible platform independent candidate for business processing.

Examples of "Tightly Coupled Monolith" and "Loosely coupled Monolith" Services:

* A service contained in the same box for UI and serves the requests, deployed in the same server (Tightly Coupled)

* A service which sits in a different box and serves to more than one UI, say Service is available to Website, Mobile App or the external services like EDI (Electronic Data Interchange) orders (Loosely Coupled)

Monolith Real time Example:

An enterprise grade bug-tracking application which may highly prefer to monolith because of it's simplicity to deploy and maintainability (Initial Process)

Let's have a fictional bug tracking application "PinPointer" which prefers to have a loosely coupled monolith architecture, so they have hosted a Web API Service in a box A and hosted a Website in box B, after the successful venture into the field, the company decides to foray into the mobile app also, since they have already decoupled the Service and the UI it is easy for them to develop the Mobile App which consumes the Web API Service and process the data accordingly without any hassle.

 

(To be continued)

 

 



   

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