Design Patterns for Microservices
<p>A pattern is a way to design an optimized structure for microservices. There are many ways we can design and build microservices. Here is a list of key design patterns used for decomposition, integration, data management, observability, and other misc. cross cutting concerns.</p>
<h1><strong>Decomposition</strong></h1>
<p>Decomposition strategies play a crucial role in determining how well it can scale and perform properly under higher workloads. As a rule, we do not want to decompose large monolithic applications and create another distributed monolithic system with its own set of issues and challenges.</p>
<ul>
<li>Decompose by business capabilities</li>
<li>Decompose by subdomains</li>
<li>Decompose by transactions</li>
<li>Decompose by service per team</li>
<li>Bulkhead</li>
<li>Sidecar</li>
<li>Strangler</li>
</ul>
<h1><strong>Integration</strong></h1>
<p>This is essentially the idea of adding more services or structuring an application so that the services are able to communicate with each other and with the client in a very efficient manner.</p>
<p><a href="https://medium.com/@dmosyan/design-patterns-for-microservices-34b2d4141465">Click Here</a></p>