Today, Redis Watch is taking the next and only obvious step in its evolution and, as of this issue edition, Redis Watch is the de-facto the only open source newsletter about Everything and Anything Redis. Are we crazy to open up everything like that? Perhaps. Will we increase the goodness in the world? Most probably. Therefore:
To distinguish between issues and issues, issues will be referred to as editions whereas issues will remain issues (newsletter’s and repository’s, respectively).
An effort will be made to port all 57 existing editions to the repository.
Ideas, submits, code contributions, feedback and general good will are always welcome.
Also, since Redis Watch is all about the community, by the community and for the community and because there’s no I in Team, we will refrain from using the singular first person pronouns “I” and “me” in this inaugural #oss edition.
Since time immemorial within the Redis community, a Moka Pot is considered a token of appreciation to a member for her/his contributions. I’d like to present this one to Didier Spezia @didier_06, who’s been – at least for us – a shining beacon of Redis expertise and a fountain of help. You need take only one look at his SO profile to understand the caliber of expert that he is, and if you take time to read through his answers we’re certain you’re learn something new. If you want just one example, here’s one from the other day: How to understand redis-cli’s result vs redis-benchmark’s result
Didier – for being #Soreadytohelp, may your coffee always taste as good as a cup of Italian Moka, thank you.
Christophe Limpalair @christophelimp, whom we fondly remember from previous Redis Watch issues, writes about our favorite topic from CodePen @CodePen‘s perspective. To power this uber-frontend, the two humble Redis servers are employed (one’s a slave, naturally) to buffer n’ squash snapshot updates, background job scheduling and easy-peasy voting. But all that pales when you get to the “Critical use cases” section where you learn how an expiry-based throttler/killswitch protects an Apache Solr engine during its bad times.
There’s more goodness in the article but one thing bothers us: we’ve heard that Redis is the Leatherman of Databases, and CodePen definitely strengthens that analogy. But if CodePen is the “playground for the front end web”, what does that make Redis? The best we could come up with is multi purpose playground equipment but perhaps you can make a catchier one.
That’s one cool viz from Salvatore Sanfilippo @antirez of 90% of commits made to Redis where “Each commit is a rectangle. The height is the number of affected lines (a logarithmic scale is used). The gray labels show release tags.”Tcl source included, naturally. We’re fascinated with data visualizations and even more so with those that are about code, so we couldn’t have agreed more with the author’s closing sentiments.
So nice to have a cheat sheet at an untracked search query easy reach – by @stephaneisfeld via @duckduckhack. The actual content is slightly, ehm, stale but we couldn’t find the sources to make a pull request for updating it… ideas?
Definitely not your plain old stuff – the POCO here means POrtable COponents, and this project is all about cross-platform C++ libraries with a network/internet focus. We’re not that heavily into C++ nowadays but it appears that the project has a lot to offer, and even more so now that it has been added with our favorite MPPE. The change is so recent that the documentation reveals nil, but our quick src inspection reveals nothing less than the beginning of a new Redis client. That like witnessing a baby being born or watching a supernova – very exciting. Good luck to @pocoproject and leader Aleksandar Fabijanic – “Old, but not obsolete” – @0x00FA. BTW, is anyone familiar with the Boost Software License?
If you know us anything about us by now, you should know that if there’s one thing that we like it is Redis. No, make that two things: Redis and data structures. Actually, there are three – Redis, data structures, Lua and trees. Wait, that’s four. Never mind. Our thanks go to Zihua Li @luinlee.
No it doesn’t. In fact, the very notion of an empty key regardless its data structure, doesn’t EXISTS in Redis 🙂 Still, realizing this post-factum while chasing gremlins is less than desirable so you’d be better off internalizing this now. Courtesy of Ben Nadel @BenNadel.
TL;DR Redis is simple but beware of asymptotic computational complexity. This first article via @Avvo‘s engineering is from their Director of Software Development Justin Weiss @justinweiss who, AFAWK, writes about the first publicly known Redis use case in the Legal vertical.
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.