Microservices.io

11 development and architecture rules for successful adoption of microservices are presented in this post.

Microservices rules: what good looks like

<p>The article is a powerpoint with these 11 roules (you will find then in the start of the page)</p>
<ol>
<li>Practice continuous delivery/deployment</li>
<li>Implement fast, automated deployment pipelines</li>
<li>Organize into small, cross-functional, loosely coupled teams</li>
<li>Provide a great developer experience (DevEx)</li>
<li>Use a rational design process</li>
<li>Design independently deployable services</li>
<li>Design loosely coupled services</li>
<li>Design testable services</li>
<li>Develop observable services</li>
<li>Incrementally migrate from a monolith to microservices</li>
<li>Track and improve software metrics and KPIs</li>
</ol>


<p>Read the book shown years ago.  So much information.</p>
