Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • 4
    Out of curiosity, is there a reason you're not using a monorepo? Some (including myself) consider that the default design since it avoids issues like this, with separate repositories being an alternative design to be used only in extenuating circumstances. Commented Aug 23, 2024 at 20:59
  • 2
    "each in a separate git repository" - try changing that part Commented Aug 24, 2024 at 17:41
  • Why does an update to a dependency translate to "change the dependency in all of the micro(services) and thus still have to commit, push, merge, release, deploy in each of them"? From the setups I know, if you need to update a dependency in the system, you just do so in the system; it’s a matter of deployment and perhaps building, not changes in the source code repository. At you statically linking all dependencies? Commented Aug 26, 2024 at 6:51
  • @MisterMiyagi Are you not versioning your dependencies? Commented Aug 26, 2024 at 8:21
  • @Bergi I’m not pinning them to specific versions to avoid problems just like that. Specific dependency versions are part of our deployment/configuration management, not hardcoded in our software/packages. Commented Aug 26, 2024 at 9:02