redigo

The author was using redigo (https://github.com/garyburd/redigo), which by my analysis is fairly performant. One of the likely causes for issues is file descriptor limits or TCP tuning that you suffer when stress testing two dependent networking apps on the same server. BoltDB, being embedded, just works out of the box.

I've been using go-json-rest, which is by way of "just enough on top of net/http to make APIs easier." https://ant0ine.github.io/go-json-rest/ Gorilla is useful, but more for its range of standalone components than as a framework. https://github.com/gorilla Then you'll want database-related packages like redigo and gorp. https://github.com/garyburd/redigo https://github.com/go-gorp/gorp

> The moment you try to use one of them that is actually an error (trying to pass it as an argument to another function without inspecting it first for example), it causes your current function to return an error. I've seen another way to do it, that works with current Go, in a redis client [1]: - Function 1 returns rawarg, error where rawarg can be anything - You want to transform arg into some type, so you create a function that takes a rawarg and an error and returns your type and an error - In the implementation of your 2nd function, if err != nil, return it directly This way, as a library user you can just chain your calls without the tedious if err != nil (it will be taken care of in the library). This might not scale to huge programs, but there certainly is a way to reuse this idea. [1] https://github.com/garyburd/redigo/blob/mast

If any gophers need a solid redis library I would recommend: https://github.com/garyburd/redigo This is a mature library that I have been using for years.