A Newsletter About Everything Redis

Issue #48
June 18th, 2015

#include i.h

Suddenly and in a totally unexpected way Redis Watch is at it's 48th issue! Did you know that 48 is the number that follows 47 and precedes 49? It is also the 0-based index of the first bit of the 7th byte in a bitstream so you can find it quite often in code (for example, Redis' current unstable branch has 48/4 of it). On a totally different matter, this week was devoid of NoSQL benchmarks, which also makes it kinda special 😉

Redis Trivia: The ambitious and epic OS Redis Rosetta Stone project – https://github.com/itamarhaber/redis-rosetta-stone /ht @microspino


Be social, tweet about Redis Watch: I'm reading Redis Watch #48: https://redislabs.com/redis-watch-archive/48

int main(int argc, char **argv) { 


OH Salvatore Sanfilippo @antirez > Dear Italian friends, I may receive a grant about OSS, I want to give it to people helping Redis/Disque. Any legal hint? Need to pay taxes?

OH Josiah Carlson @dr_josiah > Hey #Python and #Redis folks, I want to write something, but I don't know what to write about. What do you want to know?

Community Redis Aggregator #Redis #aggregator

The only thing better than knowledge is meta knowledge, which is exactly what planetredis.org is all about – the best of Redis content under the same roof. And the only thing better than meta knowledge is OS meta knowledge, which is exactly how the team at @VividCortex and "The Red(is) Baron" Baron Schwartz @xaprb had built this one – both source code and source feeds are open at GH and awaiting your PRs.

seppo0010 / rsedis #Rust #foss

It takes all kinds to make a world and in our world one of the things that make "Third Time's a Charm" Sebastian Waisbrot @seppo0010 unique is his hobby of implementing Redis. After first doing it with rlite, the embeddable Redis-like engine, we are presented with the Rust implementation. Do feel free to encourage Sebastian with implementing Redis in more exotic ways as practice makes perfect and I, for one, can't get enough of Redis 🙂

moonglum / storage-pod #NodeJS #foss

From what I've seen so far, Node.js modules fall into one of two major categories: the how-come-no-one-thought-of-that-before and the who-in-his-right-mind-would-do-this. This one lets you do just two things – store a value and get back a key, give a key and get back the value. Sounds simple? It is 🙂 Yet this is very effective for most purposes so definitely first category material – by "He Who Thunk It" Lucas Dohmen @moonbeamlabs.

Plans for Redis 3.2 (6:37.9 minutes to read)

Redis' creator "The Benevolent Dictator" Salvatore Sanfilippo @antirez outlines his plans for the next feature-focused version. Goodness begins with Matt Stancliff @mattsta's geo hashing API and Bloom filters that are a-coming (an unexpected synergy from the Disque project). If that&39;s not enough for you, there are new List operations, AOF improvements, more clustering power and, last but not least, several memory optimizations that will lower Redis' RAM overheads dramatically in some cases (shameless plug: by the extremely talented team here at Redis Labs).

Using Redis as Your Main Superfast Persistent Database in Node & Express #NodeJS #howto

"Title Author Extraordinaire" Stefan Fidanov @fidanov is also very good at writing the actual article – a recommended 3-in-1 introduction.

Redis, set, node. #NodeJS #howto

"One More Time" Kyle @stockholmux continues to set an example.

!(Ivory Tower)

OH Jan Erik @badboy_ > @antirez https://github.com/antirez/redis/blob/unstable/src/sentinel.c#L1786-L1787 – clang rightfully complains that `slave_addr` is never read after assignment.

OH Salvatore Sanfilippo @antirez > Using the clang static analyzer @badboy_ found an hard to trigger Sentinel bug: https://github.com/antirez/redis/commit/821a986643717018cad8af9f35cba49818e60294

OH Jan Erik @badboy_ > Good thing I'm studying the basics of static analysis, model checking and program verification. It has a real-world value. 🙂

Can someone ELI5 what Redis is and in what circumstances it should be used? (self.rails, 12 comments)

Considering some of the discussions on Reddit, this one turned out pretty well (I was expecting a full-out flame war, but that's probably just me being a pessimist). For the less initiated, ELI5 stands for Explain Like I'm 5yo. Participation is encouraged.

Redis Hot Patch (3:18.45 minutes to read)

Security researcher "Just Because I Can" Ben Murphy @benmmurphy latest escapade uses the same Lua vulnerability that he had unveiled a week earlier to hot patch Redis to block any sandbox escapes.

Prototyping fun with Flask and Redis. #Python #howto

A fun intro to prototyping with Flask and Redis from "I Haz Photoshop" Roberto Calderon @calderonroberto that I had actually helped with (to an extent ;)).

OH Daniel Schep @schep_ > switch to redis. holy shit that was easy

Beyond Request-Response #Django #Python #howto

Instead of sticking with the traditional request-response model, "I love Django dearly" Andrew Godwin @andrewgodwin shows how to use Redis to decouple the request from the worker serving it.

OH Bryan Downing @quantlabs > @akmalchaudhri awesome awesome awesome news on redis, screw the rest go with the best


Redis Labs

Blog Post: AppFabric Coming Apart? Top 5 Reasons to Move to Redis Labs

Guest Post: Wide-Open Throttle: Shift Your Apps to Ludicrous Speed with Redis Labs via Open Shift @OpenShift.

Redis Academy: Redis in Action, Chapter 6: Application Components in Redis

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

Archive | Subscribe | Follow on Twitter