[mementomori]

Microservices is for scaling applications that need to handle a high volume of transactions (millions+) with the expectation of high growth in transaction volume. It became a solution for Uber and Netflix when the exploding user requests caused their monoliths to become difficult to manage/modify/deploy. An application that handles hundreds to thousands of transactions doesn't necessarily have the problem that requires the microservices solution. The main tradeoff of microservices is that it increases the complexity of software, and has a lot of moving parts that need to be done right to achieve the advantage. The hype of encourage every to-do app creator to use microservices may be an overkill. The writer of the post does have the incentive to encourage the use of microservices and the utilization of their services.

[Maria_micro]

I agree with your statement, and the post explains the pros, but also the challenges of microservices. Our service does not depend on the project architecture, it can run with microservices, monoliths and hybrid systems just the same. It’s in our best interest to support all variates :)