gin

gin[1] is a popular off-the-shelf solution that provides a lot of functionality for you. But as everdev said, it's pretty normal to gradually build up your own stack using the stdlib and possibly some smaller, more focused packages like httprouter[2] and the gorilla toolkit[3]. I actually have learned a lot about HTTP/HTTPS servers by working on a lower level and building up my stack! I recommend just starting with the stdlib and importing 3rd party code where you feel yourself limited by it. The first thing people probably adopt is a more expressive router. [1] https://github.com/gin-gonic/gin [2] https://github.com/julienschmidt/httprouter [3] https://github.com/gorilla

While I'd agree that net/http is very capable, it still comes with a variety of gotchas when doing timeouts, logging, routing, etc. I think gin[1] is a good bet for jumping into building something without having to dive into doing a lot of http.Server research. [1] https://github.com/gin-gonic/gin

Gin [0] is a good place to start for Go web frameworks Gorilla [1] is more of a toolkit, but very common and very useful There's also Buffalo [2] for an opinionated kitchen sink included web framework. As for SQL ORMs, sqlx [3] and gorm [4] seem to be the most popular ones. But really the `database/sql package` is probably all you need. As for drivers, here's a list [5] [0] https://github.com/gin-gonic/gin [1] http://www.gorillatoolkit.org/ [2] https://github.com/gobuffalo/buffalo [3] https://github.com/jmoiron/sqlx [4] https://github.com/jinzhu/gorm [5] https://github.com/golang/go/wiki/SQLDrivers

It's a nice reference program to show you what's going on. I build stuff like this for a living. I'd recommend not re-inventing the wheel yourself and using a nice web framework, like Echo (https://github.com/labstack/echo) or Gin (https://github.com/gin-gonic/gin). I prefer Echo due to a cleaner, mockable design, but they're equivalent. You can throw up that web server in 1/10 the code to do the same thing, and using built-in middleware is less work than writing your own.