Vincent Driessen creates RQ as an alternative to Celery inspired by Resque:

I wanted a solution that was lightweight, easy to adopt, and easy to grasp. So I devised a simple queueing library for Python, and dubbed it RQ.

Welcome to the world of a thousand Redis-based queues.

Original title and link: Another Redis-Based Queue for Python: Introducing RQ (NoSQL database©myNoSQL)

via: http://nvie.com/posts/introducing-rq/

The nuts and bolts of implementing synchronous and asynchronous Redis clients supporting pipelining:

In this post I describe different approaches for client-libraries to implement Redis protocol pipelining. I will cover synchronous as well as asynchronous (event-driven) techniques and discuss their respective pros and cons: Synchronous client APIs require the library user to explicitly pipeline commands, potentially yielding optimal protocol performance, but at the cost of additional bookkeeping when handling replies. Asynchronous client libraries, on the other hand, allow automatic pipelining, while being less efficient in their pipelining behavior.

Original title and link: Automatic Async and Sync Pipelining of Redis Commands (NoSQL database©myNoSQL)

via: http://informatikr.com/2012/redis-pipelining.html

TL;DR:

even if Redis is an in memory database it offers good durability compared to other on disk databases.

But you must read the post for all the nitty-gritty.

Original title and link: Redis Persistence Demystified (NoSQL database©myNoSQL)

via: http://antirez.com/post/redis-persistence-demystified.html

Graham King:

On paternity leave for my second child, I found myself writing an in-memory hashmap (a poor-man’s memcached), in Go, Python and C. I was wondering how hard it would be to replace memcached, if we wanted to do something unusual with our key-value store. I also wanted to compare the languages, and, well, I get bored easily!

Actually it’s very easy and doesn’t require any coding at all. Plus you’ll get a bit more than what you’d expect.

Original title and link: In-Memory Key-Value Store in C, Go and Python (NoSQL database©myNoSQL)

via: http://www.darkcoding.net/software/in-memory-key-value-store-in-c-go-and-python/

Salvatore Sanfilippo:

Redis 2.6 support for Lua scripting opens a lot of possibilities, basically because you can do atomically a lot of things that before required to pay a big performance hit.

In this blog post I want to show a pattern based on the scripting capability that can be used to implement reliable queues.

I know I might upset a few people, but this feels like reinventing some wheels. Having server-side scripting support in Redis makes it a possible good fit for many new use cases, so I don’t think there’s a need to reinvent solutions that can already address an even wider range of scenarios.

Original title and link: Reinventing Reliable Queues With Redis Lua Scripting (NoSQL database©myNoSQL)

via: http://antirez.com/post/250

Redmonk’s James Gavernor in a sort of a documented Redis? Hell yeah!:

Indeed mentions on HackerNews is just a sign of breaking the awareness threshold. But with awareness comes adoption. The only thing that remains to be established is the relevance of the HN community.

Original title and link: Redis: Hell Yeah Take 2 (NoSQL database©myNoSQL)

via: http://www.redmonk.com/jgovernor/2012/03/15/redis-utterly-killed-it-in-2010-check-out-the-growth-in-share-of-developer-conversation/

TJ Holowaychuk:

Lua is a great fit for Redis, they have similar philosophies, being simple, small, and fast.

Hell yeah! I almost can feel it!

Original title and link: Redis Lua Scripting Is Badass (NoSQL database©myNoSQL)

via: http://tjholowaychuk.com/post/19321054250/redis-lua-scripting-is-badass

Many useful pieces of advice—from the very basics to renaming commands—in Marc Wickenden post about securing Redis:

Redis doesn’t have much in the way of security so I knew that anyone who managed to pop the box could theoretically connect to the local Redis instance and mess around. I’ll take you through the steps I took to install and harden Redis, on a Debian Squeeze GNU/Linux box.

Archived.

Original title and link: NoSQL Security: Installing and Hardening Redis (NoSQL database©myNoSQL)

via: http://blog.7elements.co.uk/2012/03/installing-and-hardening-redis.html

Interesting comments on StackOverflow:

So, honestly - Is memcache really that old dinousaur that is a bad choice from a performance perspective when compared to this newcomer called Redis?

Here’s mine: feature-wise Redis has already overpasssed Memcached in almost all aspects. Redis 3.0 will bring Redis Cluster a distributed implementation of a subset of Redis standalone—check this for an detailed explanation of Redis Cluster. Production-wise though, Memcached will not be replaced so easy as so many services rely on it for quite some time.

Original title and link: Is Memcached a Dinosaur in Comparison to Redis? (NoSQL database©myNoSQL)

via: http://stackoverflow.com/questions/2873249/is-memcached-a-dinosaur-in-comparison-to-redis

Cody Powell:

It turns out that, technically, I was correct. I could use MongoDB as a key-value store for caching, much like I could use my Mazda 3 as an amphibious assault vehicle. In practice, neither would be optimized for those use cases.

Use the same principle if you have to build MongoDB work queues.

Original title and link: Redis and MongoDB Can Work Together to Perform Distinct, Complex Queries (NoSQL database©myNoSQL)

via: http://architects.dzone.com/articles/redis-and-mongodb-can-work?mz=36885-nosql