3 ms·
I've developed/am developing an API in Go. Go's not quite mature, and it shows at times. For example, if the tcp connection underlying your database connection
by draaglom 13y ago
I've developed/am developing an API in Go.
Go's not quite mature, and it shows at times. For example, if the tcp connection underlying your database connection dies, it won't reconnect automatically.
The standard library is neat; net/http is friendly and easy to use but unless you want to spend half your time munging request.URL.Path with regexes you'll want to use a different mux / router from the standard library - there are many good ones available.
Channels make realtime (ie, websockets) quite simple, and the type system means you can iterate quickly without so much fear of introducing bugs.
I can't speak much for the performance; we haven't tested it under much load yet.
- justinzollars 13y agoI think the performance question is the one I am most interested in. Go seems to boast about its speed and efficiency. I'd be curious to know your results in the future!