Building an API with Go at Microco.sm

https://speakerdeck.com/mattcottingham/building-an-api-with-go-at-microco-dot-sm

by hebz0rl • 13 years ago

57 16 13 years ago

speakerdeck.com

redbad• 13 years ago

Nice overview. Somewhat frustrating to see non-gofmt'd code examples. Fix that up :)

motter4• 13 years ago

None of the links work in the embedded version, but if you download the PDF they're fine.

zeckalpha2• 13 years ago

18k lines? Does that seem high to anyone else? Or am I missing something important?

realrocker2• 13 years ago

It is high. Probably includes code site,docs etc.

motter4• 13 years ago

High compared to what?

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.

zeckalpha2• 13 years ago

Compared to the amount of work that needs to be done for this project to function.

ajack• 13 years ago

As a member of LFGSS and HN, yes!

asselinpaul• 13 years ago

same :)

feniv• 13 years ago

My experience has been pretty similar: Go is perfect for building high performance APIs. A lot of the library infrastructure is still in early stages.

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.

motter4• 13 years ago

Thanks for pointing that out. The static routes in the talk are just for illustration -- we use nginx to serve them in production.

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?

pjmlp2• 13 years ago

My experience has been pretty similar: Go is perfect for building high performance APIs.

Like any native compiled language, it is just a matter of having the right set of libraries available.

Herbert2• 13 years ago

Despite the overall ecosystem being rather small, the standard library and adjoining experimental packages are excellent. I wouldn't be surprised if go 1.2's stdlib would cover most of what Python's stdlib and Twisted can do.

pjmlp2• 13 years ago

Please call them web services or REST API, just API is confusing.

koblas• 13 years ago

Maybe I missed it - but it would be really cool to see a large fragment of working code for some of the apis.

Building an API with Go at Microco.sm

Related Stories