This edition begs to begin with a laudable numbers joke, but I’m refrained from doing that. Instead, let us note how May Fourth is just a play on June Third and snicker at this ripoff of what is truly a glorious day. Snicker snicker.
Salvatore Sanfilippo @antirez releases the third candidate (technically 4th?) for v4 is out with a boot-load of goodies ranging from features through fixes to improvements across the board. Barring stop-the-world issues and forces of nature, it looks a formal release isn’t too far away. Two and a half notable observations about the RC’s impressive payload:
A substantial count of major changes
The force community is strong – happy May Fourth!
More parties involved in fixing issues and contributing features
Santoro Simon had attended QCon @QCon London 2017 and took notes of what looks like an educational user story . Of particular (personal) interest was this session from Cem Staveley, but both video and presenter are untraceable to this watcher’s eye.
Nikrad Mahdi @nmahdi reviews the design of the homegrown rate limiting system that’s employed by Figma @figmadesign to protect against spam attacks. He provides a wonderfully graphic explanation of three approaches – token bucket, fixed window counters and sliding window log – in native Redis terms.
Due to security reasons, AWS’ Redis-as-a-Service is not accessible to public interfaces. While this lockdown prevents some attacks, it also makes it impossible to just connect to from, lets say, your laptop. Jamieson Becker @JamiesonBecker of Userify @userify shows how to set up a tunnel to quickly and effectively work around that issue.
While still new-ish, this looks promising in terms of functionality and robustness – a replication tool that supports slave synchronization, persistence files and the latest formats and versions. By leon.chen @chenbaoyi1.
Three well-executed simple-n-clear diagrams by Taswar Bhatti @taswarbhatti, that make it hard to miss the points of using pipelining and batching (transactions). You can safely treat the code snippets as written in some pseudo language 😉
Note to self: steal these for next training session!
My reaction to the project’s promise – “Making Redis pipelines easier to use in Python” – was: pipelines work just fine, why change anything? But after reading the (great!) docs about “a paradigm shift” to using “reusable blocks ” and “duck-typing”… well, it makes perfect sense. Pythonistas should really check this one out.
Bonus: both stand-alone and cluster modes are supported.
Then Elena Kolevska came on stage and showed us how you can improve the performance of Redis, just by reducing the number of requests, using pipelines or Lua scripts. And if you are a really hardcore developer you can go to “warp ten” by writing an extension in C. An Easter egg in her talk was that it was actually a continuation of a talk she gave last year at the Bulgaria PHP conference, which I also had the pleasure to see.
On the quest of pushing the modules API further and farther, Salvatore Sanfilippo @antirez has made blocking commands even more powerful with a thread-safe context that allows interaction with the core. Put differently, this gist shows how to implement KEYS using a non-blocking, client-blocking module command.
The one-man-wonder Dvir Volk @dvirsky, with whom I proudly share a room and many opinions, keeps pouring absolute awesomeness into his uber-module. Here’s a recap of what you’ve missed since last time:
Queries turned to level 11:
Field modifiers for creating complex filtering on multiple fields
Allow selecting multiple fields
Optional terms and clauses
Match on prefix, (e.g. Redis Watc*)
Support for NOT queries
Results are sortable by property
Queries can have payloads (to be used by a custom scoring function)
Support for dynamically loading extensions… let me repeat that: Support for dynamically loading extensions! Let that one sink in for a minute. Yes, that means the monster can haz its own modules.
When: Thursday, May 18, 2017, 5:30 PM to 7:30 PM Where:Napster @napster, 701 5th Avenue, Suite 3100, Seattle, WA What 1: Scaling with Redis for Caching and Background Jobs What 2: TBD <- feel free to approach the organizers with suggestions
Microsoft sponsored a project to port Redis onto Windows, but the project was recently discontinued according to Microsoft. What are your options now? Let Redis Labs VP of Product Management Cihan Biyikoglu @cihangirb tell you via DZone @DZone.
Redis Labs is ranked as top #4 database-as-a-service providers – fourth only to AWS, Microsoft and Oracle! – for its score in the current offering category, recognized for its ease of use, scale and high availability functionality.
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.