<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1631206797125/Doj7qTtrg.jpeg" alt="cda4db94-ac16-43ba-82c4-53632154afc7.jpg" />
Source <a href="https://www.n-ix.com/microservices-vs-monolith-which-architecture-best-choice-your-business/" class="autolinkedURL autolinkedURL-url" target="_blank">n-ix.com/microservices-vs-monolith-which-ar..</a></p>
<h2 id="definitions">Definitions</h2>
<h3 id="monolith"><strong>Monolith</strong></h3>
<p>Huge systems running entire system, need not to be single, i.e. we can scale horizontally.</p>
<p><strong>Advantages</strong> </p>
<ol>
<li>Good for small team.</li>
<li>Less complex, easy to maintain.</li>
<li>Less duplication of code.</li>
<li>Faster, procedure call is faster, cuz its within same machine</li>
</ol>
<p><strong>Disadvantage</strong></p>
<ol>
<li>More frequent deployments, as everything is interconnected</li>
<li>If server crashes, whole system will stop</li>
</ol>
<h3 id="microservices"><strong>Microservices</strong></h3>
<p>When monolith breaks into pieces called micro services. Small business unit running specific functions.</p>
<p><strong>Advantages</strong> </p>
<ol>
<li>Easy to scale, each service is concerned with some function</li>
<li>Team management is easy.</li>
<li>Parallel development is easy.</li>
<li>Analysis of service is easy.</li>
</ol>
<p><strong>Disadvantage</strong></p>
<ol>
<li>Not easy to design</li>
</ol>
<h2 id="migrate-from-monolith-to-microservices">Migrate from monolith to microservices</h2>
<p>When our product grows larger, need for microservice architecture increases, so different teams can work on different services, some changes may break the existing code. New services should be separatly </p>


![cda4db94-ac16-43ba-82c4-53632154afc7.jpg](https://cdn.hashnode.com/res/hashnode/image/upload/v1631206797125/Doj7qTtrg.jpeg)
Source https://www.n-ix.com/microservices-vs-monolith-which-architecture-best-choice-your-business/
## Definitions

### **Monolith** 
Huge systems running entire system, need not to be single, i.e. we can scale horizontally.

**Advantages** 
1. Good for small team.
2. Less complex, easy to maintain.
3. Less duplication of code.
4. Faster, procedure call is faster, cuz its within same machine

**Disadvantage**
1. More frequent deployments, as everything is interconnected
2. If server crashes, whole system will stop

### **Microservices** 
When monolith breaks into pieces called micro services. Small business unit running specific functions.

**Advantages** 
1. Easy to scale, each service is concerned with some function
2. Team management is easy.
3. Parallel development is easy.
4. Analysis of service is easy.

**Disadvantage**
1. Not easy to design


## Migrate from monolith to microservices

When our product grows larger, need for microservice architecture increases, so different teams can work on different services, some changes may break the existing code. New services should be separatly 
 



Microservices vs Monolith

System architecture is important part while we design our product.

Definitions

Monolith

Microservices

Migrate from monolith to microservices