Quick summary for those who read the comments first:<p>1) If you have an existing monolith that you want to convert to microservices, don't rm -rf your project in order to start from scratch.<p>2) Keep each microservice extremely limited in scope.<p>3) Try to avoid paying for resources that you are not using.<p>4) Have certain users and departments be responsible for specific parts of the system.<p>In other words, two simple steps:<p>1) Don't be a complete moron.<p>2) Avoid accidently getting your genitals stuck in a fan while implementing standard microservice practices.<p>This article is nothing but dot points of what defines microservices with loads of advertising thrown in.<p>You're welcome.
I would recommend the author remove the automated live chat on this website trying to sell me their services. There's nothing I hate more than trying to read an article and getting a fake chat notification.