Both monolith (mono aka single service) and microservice are the two extremes of the range of services. As extremes, they each have their own set of difficultie

Both monolith (mono aka single service) and microservice are the two extremes of the range of services. As extremes, they each have their own set of difficulties. Going from one to the other is not a panacea When monolith is too big, the next step is to break it up but going all the way to microservices is still too extreme in my opinion. Another way to think about services (mono, micro or otherwise) is to consider what one would do about a class that has grown too big with too many dependencies over time. One would most likely not jump to breaking it up into many single-method micro classes