Matt Raible
I think it’s important to be able to release your microservices independently. It seems like a repo for each service would make this easier to do than having a monorepo with all services in it. If you have teams of 10 that develop and maintain each microservice, I don’t think this is too much.
However, if you have a 1-2 people that maintain each microservice, then maybe you’re using microservices for the wrong reason. In my experience, microservices are excellent for scaling up developers and might not be needed if you’re just trying to scale up your technology stack. Some of the highest-performing systems I’ve worked with in my career have been monoliths.