Note that it's a redis serialization protocol and tcp server implementation. It's up to you to define redis commands such as get, set etc.

This can be used coupled with a backend storage to provide custom redis servers.

It's not a redis implementation by itself.

If you need an easy to write, debug, and operate RPC tech for building networked components with minimal dependencies/effort, writing Go servers with RESP (iirc, REdis Serialization Protocol) is surely the way to go. I've built several of these things (although, with a custom RESP parser), and, from my experience, the ROI is pretty high -- it's up there with bash scripts for getting stuff done.

This is a not a good way to do this kind of thing. Simple stateless redis protocol parser and an example to use it would be a much better interface.

Note that this is not a full reimplementation of Redis in Go, but rather a framework for implementing a Redis-like server in Go.

If what you are looking for is a Redis implementation, I did create a Redis v1 clone in Go a while back. It's is only a proof-of-concept and lead to the development of Redcon.

https://github.com/tidwall/sider

I reimplemented it in Java, including all the commands, with similar results. Mostly useful as a mocking tool during unit tests.

It's not a server. You can't implement a redis-compatible server in 100 lines of Go code. How did this make it to the front page of HN?

Do we really need one post a day on the frontpage where somebody reimplements something in Go?

Just because the language is really hyped right now?

Editors: can you please change the title? It's not a "Redis server implementation" at all.