re: How should go APIs be structured? VIEW POST


I've been looking for information about this topic and I came across this repo github.com/golang-standards/projec..., and taking a look to other important projects such as Kubernetes, Docker, Stripe CLI etc it seems they follow this structure, it couldn't be the "official way" but it's widely use. But I'm opened to ideas about it though 🤓.


Hey, thanks! I'll take a look for sure! I've found lots of examples of clean CLI (command pattern) style code but am still unconfident on what the recommended server api 'go way' is.

Code of Conduct Report abuse