There’s a somewhat overzealous tendency in the go community to standardize “all of the things”: naming conventions, formatting, solutions for common problems, etc… If it’s not ‘idiomatic’ it must be junk, right? The premise that every go application should be structured the same way is going too far. The task of organizing packages should be left to the developers actually working on that particular system. And certainly, the overall structure of any project should reveal a lot about the actual application. https://8thlight.com/blog/uncle-bob/2011/09/30/Screaming-Architecture.html