Redis 3.0.0 is out

From the release notes: <a href="https:&#x2F;&#x2F;raw.githubusercontent.com&#x2F;antirez&#x2F;redis&#x2F;3.0&#x2F;00-RELEASENOTES" rel="nofollow">https:&#x2F;&#x2F;raw.githubusercontent.com&#x2F;antirez&#x2F;redis&#x2F;3.0&#x2F;00-RELEA...</a><p><pre><code> * Redis Cluster: a distributed implementation of a subset of Redis. * New &quot;embedded string&quot; object encoding resulting in less cache misses. Big speed gain under certain work loads. * AOF child -&gt; parent final data transmission to minimize latency due to &quot;last write&quot; during AOF rewrites. * Much improved LRU approximation algorithm for keys eviction. * WAIT command to block waiting for a write to be transmitted to the specified number of slaves. * MIGRATE connection caching. Much faster keys migraitons. * MIGARTE new options COPY and REPLACE. * CLIENT PAUSE command: stop processing client requests for a specified amount of time. * BITCOUNT performance improvements. * CONFIG SET accepts memory values in different units (for example you can use &quot;CONFIG SET maxmemory 1gb&quot;). * Redis log format slightly changed reporting in each line the role of the instance (master&#x2F;slave) or if it&#x27;s a saving child log. * INCR performance improvements.</code></pre>

Here&#x27;s the full cluster spec: <a href="http:&#x2F;&#x2F;redis.io&#x2F;topics&#x2F;cluster-spec" rel="nofollow">http:&#x2F;&#x2F;redis.io&#x2F;topics&#x2F;cluster-spec</a><p>Looking forward to seeing it taken apart by aphyr.<p>Congrats to Salvatore and the rest of the redis committers!

(To note, I have limited experience with using Redis. My questions may be stupid.)<p>As far as I can tell, most of the advantages of Redis come from the fact that it&#x27;s all held in memory and so access is fast. Is networked access to other parts of the cluster quick enough that it is quicker than storing the data on one computer, partly on disk? When would one want to use a Redis cluster rather than something stored on-disk and cached in memory?

For lazy readers: CLUSTERING!

I just hope it&#x27;s not an April&#x27;s fool joke

Does anyone have more details on what the &quot;embedded string&quot; object encoding is and what workloads it helps with? The closest thing I can find is <a href="https:&#x2F;&#x2F;github.com&#x2F;antirez&#x2F;redis&#x2F;issues&#x2F;543" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;antirez&#x2F;redis&#x2F;issues&#x2F;543</a>, which seems pretty old.

That was a nice timing, just yesterday I hacked around asyncio-redis package to provide clustering support.<p>Anyone interested in trying it out, or contributing, you can see the project here: <a href="https:&#x2F;&#x2F;github.com&#x2F;renatomassaro&#x2F;asyncio-redis-cluster" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;renatomassaro&#x2F;asyncio-redis-cluster</a><p>Edit: as for blocking requests, redis-py-cluster is an awesome lib that provides cluster support over the traditional redis-py client.

I really like antirez approach to building system software. Build it step-by-step, iterate and very soon you have an amazing piece of software

<a href="http:&#x2F;&#x2F;redis.io&#x2F;download" rel="nofollow">http:&#x2F;&#x2F;redis.io&#x2F;download</a>

Does the cluster feature deprecate redis-sentinel?

On <a href="https:&#x2F;&#x2F;github.com&#x2F;antirez&#x2F;redis&#x2F;tree&#x2F;3.0" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;antirez&#x2F;redis&#x2F;tree&#x2F;3.0</a> branch, it shows &quot;This branch is 1004 commits ahead, 1252 commits behind unstable&quot;.

What is the best alternative for redis?

April 1st is one of the worst dates for announcements ever...

Why not just linking to the google groups post or the release notes?

Still no SSL, so using redis-client still just spews your password out all over the internet.