This is not a useful article for many reasons:
- Redis has no dependencies either
- "weird responses" from Redis? Do you change your tools the minute they don't behave the way you expect, without investigation?
- The title "Picking the right tool for the job" is the almost opposite of what's done here. It reads more like "Stumbling on cool Go software and picking what job it can do for me"
- 400 (or 850) requests/second are ridiculously low numbers for an in-memory key/value store. Redis is capable of doing 100x that on small/medium machines.