Hi Sergiy! I agree that microservices are not an simple and simply splitting an application in smaller parts and calling it a day.

It introduces new complexity due to it's distributed nature. And those are not to be underestimated, especially for teams that have not dealt with that complexity before. In those cases it's a journey. So doing microservices needs a good reason.

But microservices also solve challenges, like being able to work on a system with a larger group of engineers. Working on a monolithic system with more than two scrum teams is terribly difficult and frustrating.

So, it all comes down to understanding the context and choosing what is right for the situation at hand.