I will agree to a point. "Micro" isn't the way we should go, more of a "Macro" approach. Instead of a small service that handles one function, give me a medium service that handles a specific domain, e.g. OAuth, data retention, marketing concerns, etc. And with that said, lumping everything into a single monolith is a bad idea.

"Let's take the hardest thing in programming: factoring your system correctly, and place a network connection in the middle of it."

-t.thoughtLeadersInTech

Microservices are a terrible idea when they are "micro". 1-team-1-service is good.