An interim release on the way to wrapping up v3.2 and some squashing of issues. The upcoming RC4 will change the cluster's API to provide better docker & NAT support and then…
OH Salvatore Sanfilippo @antirez > Latest few weeks of work for 3.2 stabilization and next RCs. When I'll be done I'll focus only on threaded Redis for some time.
OOH Yuval Adam @yuvadm > @antirez i thought redis is already fast enough™ 🙂
OOH inc=[src/**/*.rs] @badboy_ > Threaded Redis ahead. What a time to be alive.
Counting words. Using Scala. With Spark. In Redis. For the win. /cc Tim Spann @PaaSDev
Dynomite with Redis on AWS – Benchmarks (~20 minutes to appreciate fully, scales almost linearly with multiple readers)
Dynomite consistently delights me and that's a masterpiece benchmark from Christos Kalantzis @chriskalan et al at @Netflix.
Charles Leifer @coleifer ain't just sitting on a cornflake, waiting for the users to come – he writes the howto and sees how they run, goo goo g' joob.
OH Rhian Lewis @rhian_is > So glad I made the effort to rewrite http://countmycrypto.com using #redis – much better performance and reliability!
The slickest IDE for developing and debugging Redis Lua scripts and probably for any other engine as well just got a wonderful shiny update from Paul Kulchenko @zerobrane – a highly recommended upgrade.
Despite the title not making sense, this is an overview and code example of using Sets and Sorted Sets for indexing values by Najeeb Shaikh @najeebshaikh via @codeproject. For more index-spiration make sure you familiarize yourself with the new-ish Secondary indexing with Redis doc page.
…is a best-effort, replicated KV store built on top of a one-hop DHT. A side project for a drop-in
#memcached replacement by Alex Dadgar @adadgar.
Cool to see two Redis-inspired engines on that list – by Dmitry Simonenko @pmwkaa.
OH alexis richardson @monadic @antirez read that as Goedel. Without which redis is incomplete.
Benoit Tigeot @Benoit_Tgt provides a good drilldown into
#Sidekiq's client connections requirements in a post mortem on an appaloosa.io @AppaloosaStore outage. Takeaways: 1) brilliant use of Slack's customizability for emojis, 2) connections are should be monitored like any other resource, 3) know the limits of your RaaS provider's plan and (I can't resist this last one) 4) switch to Redis Cloud – lower prices, more connections & alerting 😛
A performance testing tool for Redis and Memcache (atm) from @Twitter with exciting existing/future ideas up its sleeve, including rate limiting, command playback & optional heatmapability.
Useful service for instantly creating a combined log stream and a pragmatic implementation by Ben Wilber @benwilber that I find very appealing. Disappointing that the server itself isn't open source though.
Redis and @CockroachDB are designed for different purposes, so my answer to the question in the title would be "no". However, the Redis API and the abstractions that it exposes can be adopted practically by any data management system, which is exactly what's awesome about Matt Jibson @mjibson's experiment.
OH Clayton A Davis #clayadavis > Stages of #redis acceptance:
0. Why would I want an in-memory database?
1. I see how it's useful in this case.
2. This changes *everything*