// the find
tidwall/redcon
Redis compatible server framework for Go
redcon lets you build a Redis-protocol server in Go — you implement a command handler function and it handles the RESP framing, pipelining, and pub/sub plumbing. Useful when you want clients to talk to your service using any Redis client library without running actual Redis. Niche but sharp for that use case.
The benchmark numbers are real: 2-4x Redis throughput on the same hardware, which makes sense since you skip persistence entirely and Go's goroutine model fits pipelined I/O well. The API surface is tiny — one function, two types, done. The inclusion of pub/sub as a first-class primitive saves you from reimplementing it yourself. TLS support is there without any ceremony.
The whole repo is essentially one file (redcon.go + resp.go), which means when something breaks at the protocol level you're debugging it yourself with no abstraction to isolate the problem. RESP3 support is absent — if a client negotiates RESP3 via HELLO, you're on your own. The benchmarks are from Go 1.7 on a 2015 MacBook Pro, so they're a decade stale and tell you nothing about current hardware. There's no built-in command routing or middleware pattern; the mux example exists but it's a third-party add-on bolted on after the fact.