A Comparison of Go Web Frameworks (2014)
corner.squareup.com
A Comparison of Go Web Frameworks (2014)
1–10 of 28 posts
Re: A Comparison of Go Web Frameworks (2014)
#2Re: A Comparison of Go Web Frameworks (2014)
#3Re: A Comparison of Go Web Frameworks (2014)
#4Re: A Comparison of Go Web Frameworks (2014)
#5Articles on Go web frameworks all end up at the same conclusion. The Go standard library is so strong around web servers it's hard to recommend anything else.
Writing full-featured web apps in Golang in 2015 is still a lot like writing a Sinatra app was 8 years ago. It feels great at first, but you quickly realize that you're just building a half-assed version of Rails.
Re: A Comparison of Go Web Frameworks (2014)
#6Re: A Comparison of Go Web Frameworks (2014)
#7Re: A Comparison of Go Web Frameworks (2014)
#8https://github.com/justinas/alice
It's not very much code (only ~90 lines inc. comments), but I think it establishes a pattern that makes everything very straightforward from authentication to logging to runtime analysis. Plays very nicely with gorilla. I think the more you let net/http shine, the better.
Re: A Comparison of Go Web Frameworks (2014)
#9You may also want to take a look at beego ( https://github.com/astaxie/beego ). It introduces a lot of workflow features on top of routing. Also, you may have an easier time with it if you can read Chinese.
Re: A Comparison of Go Web Frameworks (2014)
#10https://ant0ine.github.io/go-json-rest/
Gorilla is useful, but more for its range of standalone components than as a framework.
Then you'll want database-related packages like redigo and gorp.