redis 2.6 is finally out and i think that now that we reached this point we'll start to see how the advantages of a release that was already exploited in production by few, will turn into a big advantage for the rest of the community.
scripting, bitops, and all the big features are good additions but my feeling is that redis 2.6 is especially significative as a step forward in the maturity of the redis implementation. this does not mean that's bug free, it's new code and we'll likely discover bugs especially in the early days as with every new release that starts to be adopted more and more.
what i'm talking about when i say redis 2.6 is more mature is that it is in general a more safe system to run in production: latency spikes due to mass-expire events or slow disks are handled much better, the system is more observable with the software watchdog if something goes wrong, monitor itself shows commands before their execution and as they were sent by the client, slaves are read-only by default, if rdb persistence fails redis stops accepting new writes by default, and i can continue with a list of features and fixes that are the result of experience with bad behaviour in production of the 2.4 release.
now the followings are the tasks at hand:
* redis sentinel
* redis cluster
* redis 2.8
* all the small advantages that will make 2.8 a safer release compared to 2.6
i don't want to comment too much but let me say this: in the next months you'll see redis cluster to become reality.
for now we can enjoy redis 2.6 and see how our wondeful community will take advantage of it :-)comments