Awesome-Linux-Software VS exposure-notifications-server

Brazilian Portuguese version : here.

Not a small one, but a real-life one, the exposure-notifications-server is usually what I like to recommend, keep in mind that you probably need a bit of Go knowledge and context before looking at it so perhaps it isn't the best introductory project to look at; however I recommend you to bookmark it for future reference.

Google's Exposure Notification Reference Serve is a real life example of what you're asking for.

It's also popular to hate on golang-standards/project-layout here (mostly due to its misleading name), but then you'll find Google's own project following its general approach.

Context logger (https://github.com/moonr-app/crypto-signal-trading-bot/tree/main/internal/shared/logging) inspired by the one Google wrote for the Covid 19 server (https://github.com/google/exposure-notifications-server)

Other redditors mentioned some good resources, I'm going to shamelessly plug mine as well; either way after you are done with whatever tutorial you use I recommend you to look at the Exposure Notifications Server, reading the source code should help you learn other best practices.

No worries, I was just saying isolate any database related operations specific to a package. https://github.com/google/exposure-notifications-server this is a pretty great example of a real world sql /go.

You may want to checkout the "Exposure Notifications Server" project; I also have a similar (educational) project that uses the Repository Pattern.

However, IMO, the closest to an "official" layout would be the "Exposure Notifications Server" project, but even then I think it really depends on the business domain of your project which in the end affects naming and the final project structure.