• In a single server configuration, HyperDex is marginally faster than redis at GET and PUT.
• SEARCH looks like it can be much faster on HyperDex. I don't search, but I do keep some ancillary mappings from secondary attributes to keys, I could lose that with a good SEARCH.
• redis has a richer set of data types and operations, in particular I would miss the server side atomic EXEC of Lua code¹.
• HyperDex uses a schema as opposed to the free form of redis. That's ok for me. I like to make rules about my data.
• If you plan to go beyond "in RAM" sizes, redis won't work.
• Should I be so lucky as to need multiple servers, it feels like HyperDex would scale better, but it is early days for redis clustering so that would need to be assessed at that time.
• I'm not seeing a wire protocol documentation for HyperDex. I think because there must be logic in the client end for hyperspace hashing. The wire protocol is a beautiful thing if you live in a strange world of insane performance goals achieved with asynchronous threading. You can just toss the supplied libraries and write your own. It will probably take a full port to figure out if there are problems with the HyperDex API in my world.
So what it comes down to is, I'm not switching now, but I like what I'm seeing and will give it a spin and be ready to move if I need to.
␄
¹ In practice, the unprotected nature of redis means code out front anyway and I can move the logic out there, but that is nonblocking C code for me and it is a lot easier to write the logic in Lua that gets atomicity for free, plus probably faster since it doesn't have to shuttle data back and forth to my process.