Two examples of structuring a Go application based off a talk at the Belfast Gophers October 2018 meetup.
This is close to a standard mvc layout but with domains split to separate files and a flat dependency structure.
Good to mid size projects but after 15 or so domain objects it can become a bit harder manage and browse as the files are split across separate packages.
Is closer to a DDD style layout with each domain having it's own package with handlers, service & data access siloed in each.