Anatomy of a go web application

[Tim Shannon]

I just finished writing a blog post to give an overview of building a web application in go.

http://tech.townsourced.com/post/anatomy-of-a-go-web-app/

It was kind of an excuse to play with hugo, but hopefully there's some good information in there as well.

Any corrections, or input from the group is greatly appreciated.

Thanks,

[Egon]

See these:

https://medium.com/@benbjohnson/standard-package-layout-7cdbc8391fc1#.pfyl876hg

https://www.youtube.com/watch?v=twcDf_Y2gXY

https://github.com/marcusolsson/goddd

https://www.youtube.com/watch?v=WpkDN78P884

https://forum.golangbridge.org/t/comparing-the-structure-of-web-applications/1198

https://groups.google.com/forum/#!msg/golang-nuts/1z5kL5FCDdU/Zq6l0jUzAwAJ

tl;dr; the decisions you showed are not valuable in the program, they are just artifacts of programming, by implementing and placing them first you end up hiding the valuable aspects of the software -- i.e. what benefit does it provide for the end user.

+ Egon

[DrGo]

Thanks Tim,
Very nice overview of the mechanics of a web app.

[Tim Shannon]

FYI, I've added a second post that gives some specifics on Authentication and password handling, if anyone is interested.

http://tech.townsourced.com/post/anatomy-of-a-go-web-app-authentication/