11–16 of 16 posts
I really like 2 new features in 2.4:
- variadic versions of functions to reduce pipelining. This will reduce latency in my write-happy app
- memory optimized memory sets that will saves me money on RAM.
Thanks Salvatore and Peter!
antirez -- looking good. But may I ask why the name 'redis-trib' -- what does the trib mean? Short for contrib? Tribune? All I see is the nsfw definition, but maybe that's just me. http://www.urbandictionary.com/define.php?term=trib
Reading about Redis Cluster, I am a bit worried that some re-invention of core erlang features is going on. If nothing else, an erlang to redis bridge might make for a nice pesudo-cluster...
The title is a bit misleading :) This is just a preview of Redis Cluster, it's not good to just claiming that I'm working at it, I wanted to show the first stuff we have that users can actually play with (but not use in production environments!).
Reading about Redis Cluster, I am a bit worried that some re-invention of core erlang features is going on. If nothing else, an erlang to redis bridge might make for a nice pesudo-cluster...
Like execution is more important then idea in a startup, implementation in the right "scope" and with the right tradeoffs is more important than idea in a software system. So while for sure Redis Cluster will look a lot like any other distributed hash table I think it is important that we implement it inside our system, with our system language, and with Redis specific tradeoffs.
Thanks for the reply.