>  기사  >  데이터 베이스  >  Redis 2.6 is out!

Redis 2.6 is out!

WBOY
WBOY원래의
2016-06-07 16:35:57917검색

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. Scri

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
성명:
본 글의 내용은 네티즌들의 자발적인 기여로 작성되었으며, 저작권은 원저작자에게 있습니다. 본 사이트는 이에 상응하는 법적 책임을 지지 않습니다. 표절이나 침해가 의심되는 콘텐츠를 발견한 경우 admin@php.cn으로 문의하세요.