My experience with micro-services is code-bases that have prematurely adopted the pattern. Based on this, my advice is as follows... You can deploy the whole p

My experience with micro-services is code-bases that have prematurely adopted the pattern. Based on this, my advice is as follows... You can deploy the whole platform and/or refactor to a monolith, and maintain one change log which is simple. That however has its own downsides, so you should find a balance. If you're having trouble keeping track, perhaps re-organize. I read on one HN article that Amazon had 7k employees before they adopted microservices. The benefits have to outweigh the costs. Sometimes the solution to the problem is taking a step back. without more details its hard to say. So basically one option is refactor [to a monolith] and re-evaluate the split such that you no longer have this problem. Just throw each repo in a sub-folder & make that your new mono-repo & go from there, it is worth an exploratory refactoring, but not a silver bullet.