If you take microservices to mean more isolated and lightweight runtimes and moving away from “single bigass server”, then disagree. I remember multihour deployments where each team would have to stage and coordinate their rollouts with each other and it sucked, no one liked it.

If you mean how Uber famously had like 8000 microservices, more than 1 for each engineer, then sure. But it’s mixing up cause and effect. Aligning deployment boundaries with domain boundaries is, all things equal, a good idea. ZIRP-gorged unicorns would have found makework one way or another.