Some other commenters have discussed it, but one thing to make very clear that I think a lot of people are missing:
1. I fervently believe, after having lots of experience with both microservices and monoliths, that microservices do not provide any technical advantage over monoliths. If anything, they can make a lot of technical details more difficult.
2. Microservices, however, can solve some particularly thorny organization problems for large teams with respect to how these large teams build complex software systems.
Thus, in my experience microservices can serve a useful purpose, but they will only be as successful as your organizational-wide communication is.
Furthermore, for the developers replying "I don't see why I'd ever use microservices for project xyz", well, if you're a team of 1, there is hardly ever a need to use microservices.
1. I fervently believe, after having lots of experience with both microservices and monoliths, that microservices do not provide any technical advantage over monoliths. If anything, they can make a lot of technical details more difficult.
2. Microservices, however, can solve some particularly thorny organization problems for large teams with respect to how these large teams build complex software systems.
Thus, in my experience microservices can serve a useful purpose, but they will only be as successful as your organizational-wide communication is.
Furthermore, for the developers replying "I don't see why I'd ever use microservices for project xyz", well, if you're a team of 1, there is hardly ever a need to use microservices.