[thinkersilver]

This feels all to familiar to a Java developer and similar to what they do in k8s with the genericapiserver component but not to the full extent described in the article. It's interesting to see how the service container pattern appears in other language ecosystems. The nice thing about go's module system is that it feels like a monorepo without the tooling feeling separate to the language. So splitting up a repo into different repos doesn't come with the versioning hell when working with maven

[cmckn]

> So splitting up a repo into different repos doesn't come with the versioning hell when working with maven.

Damn you hurt me with this one. You can use 100 plugins and versioning with Maven in these scenarios is still a rat's nest. But using a monorepo can make CI/CD for individual services just as messy :(

[lmm]

What versioning hell is that? I've found maven versioning really nice.

If stuff is versioned together, keep it in the same repo, but in a multi-module project. If you want independent versioning you need to have an actual interface (meaning semver, backwards compatibility checking etc.) and that's the point where the pieces should live in separate repositories.