First and foremost I’d like to welcome our newest subscribers who have joined from Redis Weekly – if you do not wish to receive Redis Watch in the future, please unsubscribe using the link at the bottom. I also want to thank François-Guillaume Ribreau for his amazing years-long contributions to the community, and wish him only the best in all his future endeavors.
With Redis aligned to run on ARM devices, Salvatore Sanfilippo @antirez had added a new documentation page at redis.io that includes relevant notes and some performance figures (hey, why no #PiZero?!?)
Between this and that, señor Dvir Volk @dvirsky put together a thingamajig that adds command-line TAB-completion to redis-server and redis-cli in bash. To use, just save and source the gisted script from your .profile file.
Another useful gist from Dvir Volk @dvirsky that should be come in handy for anyone who wants to develop her/his own code that shards into hash slots like Redis Cluster does. The author had used advanced techniques to generate this and promises the sequences are the shortest possible, making it ideal for embedding in with minimal stack overhead.
If you’re lucky enough to have an Android phone, David Martínez @vaites and Termux @termux just made it possible to run Redis on it (although this does not leverage the new support for ARM). Is that a Redis in your pocket or are you just happy to see me?
A tale by Kurt Norwood @kortox of Amplitude @amplitudemobile that shows the power of server-side scripting with Lua, cutting latency and improving concurrency. The thing to remember is that even if your Redis topology is different than Kurt’s, Lua is still the best way to go for composing commands and reducing the number of network round trips.
Don’t let the title fool you. Yes, everybody probably knows that Redis’ Sorted Sets are the natural choice for leaderboards, but in this article author dmitrypol @dmitrypol includes an extra clever trick: using Mongoid for the mapping.
Doing analytics on 2 million messages per minute is, to say the least, challenging. Once you choose at-least-once message delivery semantics, like the Tapjoy Engineering @TapjoyEng team have, detecting and discarding duplicate message can become a real pita of their Kafka-Spark-Postgres pipeline.
Enter Redis and ♥ Aaron Pfeifer @obrie‘s recounting of how it is used to dedupe transactions. To save on RAM overhead, Hashes are used as containers. To increase performance, Lua is employed to bring the CPU to the data.
Note: I’m somewhat ambivalent WRT the team’s approach to scaling – application-side sharding is so 2013 😉 But then again, that really depends on your Redis deployment and Redis-as-a-Service provider 😉
Even if you’ll end up writing your own code and deploying it on a different cloud this is, at the very least, a nice overview of Lambda architecture’s principles. Redis in the Speed layer is the natural choice (and this isn’t another drug reference) – via CodeProject @codeproject.
Omer Levi Hevroni @omerlh from Soluto Engineering @SolutoEng is using Redis from my favorite Redis-as-a-Service provider for many purposes, but he has a feature request that we’ve yet to provide: emailing multiple recipients when a subscription’s resources are about to be exhausted. I’ve already notified our PM team, but until we roll out this feature and for any other monitoring needs that you may have here or anywhere else have, Omri was kind enough (after gentle prodding ;)) to share his solution that uses webdis and a Nagios @nagiosinc/Icinga @icinga plugin that he wrote.
Grab Engineering @grabengineering tell how they tracked down an unexpected behavior concerning cached unicorns, key expiration and the use of slaves… but as noted in the comments by the creator, this was first reported by YouPorn years ago (albeit minus the unicorns one should hope). That said, it is still an important lesson learn, so make sure you read it all the way through (including the footnotes, and especially the 1st one).
Dvir Volk @dvirsky is diligently adding features, optimizing, crashing bugs and delighting users with RediSearch. Over the last months this module has have had several releases, the latest of which is above. Partial aggregative changes log:
Has its own extensions!
Numeric query filters
New advanced query filters: INKEYS, INORDER & SLOP
Supports updating documents
Document payload storage
Unicode aware case-folding in auto-complete searches
When: May 30 – June 1, 2017 Where: Marriott Marquis, San Francisco
Join us for the largest gathering of Redis users and experts. Explore Redis capabilities in a range of use cases including machine learning, IoT, analytics, personalization, streaming, metering, artificial intelligence and many more.
Register before April 15th, 2017 for a chance to win a $500 Amazon Gift Card.
Recently, AWS announced the availability of I3 instances across 15 different regions. We were happy to be a part of their I3 instances beta program and used our own Redise Flash technology to extensively test and benchmark the new instances before they were formally launched.
In the Forrester Wave™: In-Memory Databases, Q1 2017 report that was published last month, Redis Labs was named “Strong Performer” and received the highest ratings for key criteria such as performance, analytics support, and use cases – download your complimentary copy from our website.
By continuing to use this site, you consent to our updated privacy agreement as described here. You can change your cookie settings at any time as described here but parts of our site will not function correctly without them.