alt Hacker News> The tedium of making branches / commits / pull requests across 6 repos to land a feature is less problematic to an agent.
You're probably not using your microservices correctly if you need to change more than one service at the same time. The whole point of microservices is independently developing and deploying the services. Sweeping changes like that should be done in pieces, one service at a time.
Which is why microservices are best for larger organizations, because it reduces coordination between dev groups.
if service A calls service B, and service B adds a new endpoint, or a new optional argument, service A needs an update to take advantage of it
if a library is used by multiple services, and gets an important bug fix, each service using the library needs to update to get the fix
these are sequences of changes, not literally at the same time or requiring deployment coordination, but when this happens a lot people start asking about monorepos