Building an API with Go at Microco.sm(speakerdeck.com) |
Building an API with Go at Microco.sm(speakerdeck.com) |
One suggestion: Don't bog down your application server with serving static files (Slide 7. favicon and robots.txt). I put all of my css, js and image files in a /static sub-directory and configured nginx to serve any URL starting with /static without hitting my go-server.
One thing I haven't touched on at all is html template rendering, something I'd like to take a look at in detail at some point.
Would like to hear more about your experience with Go -- is there a writeup somewhere?
Like any native compiled language, it is just a matter of having the right set of libraries available.
It's just the output of
wc -l `find microcosm/ -name *.go`
so is really just a rough indication of the size of the project.In hindsight, I should've left this number out. It was intended to give background to the overall program size, but it's a small detail that shouldn't be the focus of this discussion.