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

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