Recent weeks have plagued us with reports about databases being hijacked for ransom by attackers. While this isn’t really news – this has been going on for years now – there is indeed a scaling trend in the number and severity of attacks. I compiled this little chart from Shodan @shodanhq data – can someone please explain how come there are so many 3.2+ instances?!?
We getting near the GA of the next major Redis version, and major it is indeed. Ken the WarriorSalvatore Sanfilippo @antirez highlights some of what’s in scope: replication v2, LFU cache eviction policy, non locking code>DEL and FLUSHALL/FLUSHDB, mixed AOF-RDB format, the new MEMORY command and… MODULES! MODULES! MODULES!
Have you ever wondered what other people are doing with Redis? Well, we have and our VP Product Marketing (((socialeena))) @leena_joshi2015 did a stupendous job in cajoling responses from the open source Redis community and Redis Labs’ customers.
Salvatore Sanfilippo @antirez in a session about Redis’ view of security (“not our problem”), insecure default security settings that “just work” and the complete recipe for unleashing a fecal tornado. Watch this if you want to understand the underlying reasoning and future direction of security and Redis.
Most Redis users never need to concern themselves with memory fragmentation, but there are cases where it becomes and ugly and expensive fact. While fragmentation isn’t a Redis-specific issue per se, the only way to defragment an instance’s memory is to reboot it (ouch). Or rather, that was the case until this pull request by Redis Labs’ Oran Agra was merged. Going forward, the built-in defragmentor (disabled by default) can remake a whole out of the Swiss-cheese that your server’s memory had become.
Udi Kidron of @Datorama tells about the migration of their centralized data store. The change, motivated by the desire to reduce operational overheads, was done gradually so the team was able to reduce risks and develop optimal solutions for each challenge they encountered. What I like best, however, is how the Redis community had helped, in this case the community being Redisson‘s Nikita Koksharov – well done 🙂
Give a man a fish and you’ll feed him for a day; give a developer the Redis modules API (and the promise for fame and fortune) and you’ve got yourself a hackathon! With five winners and over 15 finalists, it was definitely a great experience 🙂
There are only a handful of experiences that are more rewarding and educational than solving real production issues. That experience, however, often entails turning your hair prematurely gray and responsible adults have been known to be reduced to slobbering babies by it. To reduce your personal risk and save your mane’s natural RGB value, you’d be wise to heed the lessons learned over the course of more than 6 Redis production years at trivago Engineering @trivago_tech as told by Andy Grunwald @andygrunwald.
The winning entry of the aforementioned hackathon is a Redis module that provides rate limiter based on the generic cell rate algorithm. More from the module’s author, Brandur @brandur, on the why, how & what in his guest post in our blog – redis-cell: a Rate Limiting Redis Module.
Gryadka is a minimalistic reliable master-master replicated consistent key/value layer on top of multiple instances of Redis. Using 2N+1 Redis instances Gryadka keeps working when up to N instances become unavailable.
Its core has less than 500 lines of code but provides full featured Paxos implementation supporting such advance features as cluster membership change (ability to add/remove nodes to a cluster) and distinguished proposer optimization (using one round trip to change a value instead of two).
Every time you go online searching for the solution to your problem, you can make the world a better place if you write up your findings. That is exactly what Hector Yeomans @h_yeomans did after surviving his own battle of wits against security certificates and silent exceptions.
Chaos testing is a great way to make sure that you’re ready for that horrible moment when everything goes to hell in production. This useful idea is implemented by Vishwas Lele @vlele at AIS @aisteam in a fork off the Windows fork of Redis.
When: Tuesday, February 7, 2017, 5:00 PM to 7:30 PM Where: 30 Ibn Gabirol St., 3rd Floor, Tel Aviv-Yafo What 1: Containers, Docker, Swarm & Kubernetes What 2: Azure Redis Cache Organizer:Eran Stiller @eranstiller via Microsoft Azure @Azure
When: February 14, 2017, 10:00 AM to 5:00 PM Where: Talkhouse, Hangar 12, The Tel Aviv Port
Redis Day a gathering for everyone interested in the fastest open source in-memory database. Join the community of Redis
users and developers to hear their stories and learn about what’s new. The agenda includes:
Users of Redis Labs Enterprise Cluster rejoice – much awesomeness is wrapped into our latest release, including: Redis v3.2, multiple active proxies, Flash/SSD support (preview 2), role-based administration, ?-able consistency and a whole lot of internal optimizations and removals of undocumented features.
Our Mountain View and Tel Aviv offices have a multitude of open positions, including: developers & hackers, solution and support engineers, sales and marketing – apply today (and say that I sent you ;))
Questions? Feedback? Anything you want to share? Email or tweet me – I’m highly available 🙂
This newsletter was produced and distributed by Redis Labs, Inc.
Redis Labs, Inc. 700E El Camino Real, Suite 170, Mountain View, CA 94041
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.