5 ms·

I have had this issue with my current golang projects. I haven't found any clear standard for project layout. We have a bunch of microservices with grpc api end

I have had this issue with my current golang projects. I haven't found any clear standard for project layout. We have a bunch of microservices with grpc api endpoints, and some which are event driven. Has anyone found a better resource? As it is, even our internal projects are fairly inconsistent in their project structure, which is a bit annoying.

konart 6y ago
There is no such thing as a standard here. In our team we have most projects structured like this: /project-folder | |__/build (/.gitlab-ci for projects moved to our own gitlab instance) | |__/cmd (folder for your entrypoints. One or more if your projects generates more than 1 binary) |__/bin_name1 |__/bin_name2 | |__/internal (folder for your sources packages) |__/config (package config) |__/http (package HTTPServer, api, etc) |__/api |__/models |__/database (package database) |__... | |__/api (swagger and such) | |__/docs (godoc) | |__/.golangci.yml | |__... Something like this.