Don't start with microservices – monoliths are your friend
Someone please write an article, &quot;Don&#x27;t start with architecture some dude suggested because of their ego&quot;. 
There are cases when monolith is bad, and when microservice is the must.
Take the healthy approach.<p>The article is garbage with no real understanding how real microservices works:<p>The deployment:
Modern microservices are working using templates. You deploy it using that directly from you gitlab&#x2F;github. You copy paste your artifact and it&#x27;s there. The builds are taking 2 minutes to build, sometimes less, means you can quickly react on some issue as opposed to 30 minutes old school java monolith. Deployments are build in the same cluster you use for everything else. CI job runner is just another application in your cluster. So if your cluster is down, everything is down.<p>The culture part:<p>We use templates, where you have all the libraries , tracing in place. In fact when this request is coming we have some similar functionality written, so we reply to product, oh, this feature is very similar to feature X, we&#x27;ll copy it, while we discuss some schedule thing our developer renamed similar project did commit and it&#x27;s already deployed automatically to the dev cluster, the rest of the team joined to development. There is a bad pattern when you need to update your templates. This is tradeoff of approach, you don&#x27;t libraries as a concept. Hence that you can have half services migrated, half services don&#x27;t, that&#x27;s a bonus. The cons is that you need scripts to push everything immediately.<p>Better Fault Isolation:<p>Yes, you might have settings down and core functionality working, means you have less SLA breaking events. Saves you money and customers.
Same thing with error handling. If it&#x27;s just tooling you copy paste a different set of tooling. If the error logging is not implemented in a proper way in the code... It&#x27;s no different from monolith, it&#x27;s just errors in code. But things like tracing are already part of the template so for basic evens  handlers are traced from deploy #1.