Microservices have a specific purpose, to solve a specific problem. And the problem they solve *is not one most development projects face*. IT shops are doing a lousy job at identifying where and when microservices architecture actually makes sense for them. Microservices have ROI in those scenarios, but as you allude to they have massive up front costs and if you aren't getting the benefits they deliver - specifically, solving for a shared dependency issue, and various scalability and availability issues - you are going to spend a lot of resources and get little value. Yes, Netflix has a huge shared dependency problem, no, your 5 developer shop writing an internal reporting and governance tool does not.

J.Ja