Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

This post explores the misconceptions and true definitions of monoliths, microservices, and serverless architecture. It discusses the characteristics of each and how they can be scaled or shared.

Monoliths, microservices, and serverless aren't what you think they are

<p>While I agree, that the definitions are not 100% clear, it feels mostly a strawman argument. His definitions also didn’t match up with e.g. what you find on Wikipedia. I don’t care how you ‘label’ a system. For me the difference is simple:</p>
<ul>
<li>Monolith vs Microservice: Can you deploy it independently (that is for me the test of a loosely coupled system)</li>
<li>Microservice vs Serverless: Who is responsible for the infrastructure scaling? Is it your problem or the hosting provider’s problem?</li>
</ul>
