I recently got back from Gophercon in San Diego and am still excited about the talk on the Athens Project. For those unaware, the Athens Project is a module proxy for Go! It’s currently in beta, but showing a ton of promise already.
Go’s dependency management has changed a lot over the past few years. For simplicity, Go allowed you to simply specify your dependencies in your code as an import.
go get would then get all the dependencies that your application needed. This worked, for a while, but as dependency versions began to churn, we began to see issues with this pattern — especially due to the fact that Go really wants you to follow SemVer, but not all developers were.
With Go 1.11, we finally got access to modules (but they’re still experimental). Go modules allow us to specify our dependencies in a
go.mod file, similar to a Maven file or
package.json in the frontend world. The benefit of the mod file is two-fold. We have an actual package management solution that now ships with Go (as opposed to third-party tools), and we can now easily specify our dependencies and their expected versions via our
Enter The Athens Project
Now, we have a new tool that fits into our Go stack — Athens. Athens is a proxy for Go modules, similar to a tool like Artifactory. Athens is open-source and there is a public proxy available, however, you can run your own Athens server, too. This is great if you have private packages behind a firewall or if you want to keep a local module cache on your machine.
Athens seems like the next logical step towards maintainable Go dependencies. The module cache allows us to maintain specific versions, even if the hosted repo removes the commit or tag, for example.
Athens is a project that I’m excited to see grow and hopefully, you are too! If you’re interested in contributing to Athens, their Github repo can be found here. Alternatively, if you just want to use Athens, you can find their documentation here. Lastly, if you want to find more of my posts on Golang, you can do so here. Thanks!