How to design software architecture for startups
I hate to be the guy who says &quot;you aren&#x27;t doing services right,&quot; but... you aren&#x27;t doing services right.<p>&gt; Each service has to be maintained and deployed and increases the boilerplate needed for shared data structures, complicated communication protocols and infrastructure. By the time we released our app, the common library used by most services has been updated over a hundred times. And every service has to follow suit eventually.<p>Shared data structures? Common library? Services have an <i>API</i>. If you are sharing data structures and a common &quot;core&quot; library across services, yes, you are officially doing it wrong. From the architecture diagram it also looks like there&#x27;s only one MongoDB instance, which, if you have multiple services talking to the same database[0], is <i>also</i> a major sign that you&#x27;re doing it wrong.<p>IMO the author came to the correct conclusion, that monoliths are better for a new project, but for the wrong reasons. Or maybe the right reasons which aren&#x27;t clearly explained, which is that at the beginning you don&#x27;t have a good enough grasp of the domain to properly separate into independent services.<p>[0] yes, there are exceptions where you can have multiple services use the same physical database to reduce maintenance overhead, but enforce separate ownership through different logical databases or even table-level permissions, but I&#x27;m assuming that wasn&#x27;t done here.