I get that microservices are trite, and most people think they need them long before necessary; however, they have uses beyond scale.
I'm sure that there are ways to mitigate every point I can make within monoliths.
My points are just opinions.
This is what I do for a living, and I am regularly but-but-microserviced by people who are equally ignorant of competent application design and who think that breaking it into HTTP-intermediated chunks will solve that they are choosing to write bad code. That segmentation doesn't--it does nothing. It isn't YAGNI, but YAHYBDI, and I'll get hot under the T-shirt occasionally 'cause people who read discussions like this will get the wrong idea and stick their hands into the saw, too.
I could get paid more by letting people mangle themselves, but it'd be mean.
There's the occasional case where a single language won't fit the bill, but there's a big difference between 2 services and 200.