gin

Before: package main import ( "net/http" "github.com/gin-gonic/gin" ) var r *gin.Engine func handle(ctx *gin.Context) { ctx.String(http.StatusOK, "Hello, %s!", ctx.Param("name")) } func init() { r = gin.Default() r.GET("/hello/:name", handle) } func main() { r.Run(":8080") } After: package main import ( "net/http" "github.com/eawsy/aws-lambda-go-net/service/lambda/runtime/net" "github.com/gin-gonic/gin" ) var r *gin.Engine func handle(ctx *gin.Context) { ctx.String(http.StatusOK, "Hello, %s!", ctx.Param("name")) } func init() { r = gin.Default() r.GET("/hello/:name", handle) go http.Serve(net.Listener(), r) } func mai

Matt, there a tons of frameworks at different levels. There are ones like Beego (https://beego.me/docs/intro/) that others have mentioned that have all the batteries included. Others like Gin (https://github.com/gin-gonic/gin) that have a lot built in and offer an stable API and good performance. Gorilla (http://www.gorillatoolkit.org/) offers pieces you tie together but are at a lower level of abstraction. If you use the standard library, you have to build a little bit more, but you do not have to deal with dependencies or changes in 3rd party APIs.

There was a discussion about Iris on the github issue tracker of Gin, another framework, dated March 13 2016: https://github.com/gin-gonic/gin/issues/560 Some benchmark were made too.

thanks. I should have said https://github.com/gin-gonic/gin specifically vs. just generic golang. Good point!

RoR is an awesome framework that has (almost) everything you need to build monolithic web apps. Go is a different story. You need to join the pieces together to make something functional. You will probably need: - A router like [Gin](https://github.com/gin-gonic/gin) - A [XSRF token generator and validator](https://github.com/golang/net/blob/master/xsrftoken/xsrf.go) - An ORM like [Gorm](https://github.com/jinzhu/gorm) or [XORM](https://github.com/go-xorm/xorm) - A template lib like the one that comes with the stdlib - Node for front-end (ugh, this is the harder part) - The testing library in stdlib plus maybe [testify](https://github.com/stretchr/testify) - etc... Many nice things are missing. Some were [shamelessy copied by other people](https://github.com/go-testfixtures/testfixtures). Some you may need to implement yourself. The big a

I'm not sure this is the case, at least not according to the benchmarks in the gin-gonic/gin repo. This framework was submitted to HN before:https://news.ycombinator.com/item?id=9296524 In that discussion the author of gin mentions gin has a zero allocation router as well https://github.com/gin-gonic/gin/issues/249 On mobile right now, will look at the gin/echo benchmarks later (especially if the gin benchmarks compare the fasthttp engine of echo)

Is there much difference between Lion and the router in Gin (https://github.com/gin-gonic/gin)?

I personally use gin https://github.com/gin-gonic/gin and have never looked back