Yep, I remember working at a place where one team churned out a large majority of the microservices and the other three teams just kept on doing their thing.
The microservice team were especially terrible because the did all the initial work and basked in the "glory", but when it came to maintaining the services, they wanted nothing to do with it.
At some point it just doesn't scale for the team that owns all the micro services. It's poor organizational decision making to have this setup.
Sure a monolith that does 1000 things might not be ideal, but 100 repos for 100 micro services owned by a team of 5-10 devs is unmanageable on the other end of the spectrum. Oh and everyone forgets the orchestration layer.
