Redis is really cool, I can think of lots of uses for fast and lightweight and there's at least one project where it would have saved me a lot of effort if it had existed then!
Watch out for the Python library though! It doesn't even try to sanitize key names so malformed names cause all sorts of problems (including executing arbitrary commands). Plus unicode strings with non-ascii chars cause it to blow up.
All very easy to fix of course, as soon as I get a chance I'll submit a patch if it hasn't already been done by someone else by then.
Hello almost, I don't know Python so I'm not sure about this problems, btw starting from Redis 1.1 the client libraries will no longer be included in the main project (now they are in the tarball of Redis), and I'll try to stimulate much more a Bazar development style for client libraries.
Btw the Ruby client lib is solid, like it appears to be the Java one. Still there are client libs that absolutely need to be improved.
Currently the Ruby one is as far as I know the only one supporting consistent hashing but probably this problem will be fixed with the introduction of a new daemon 'redis-cluster' that will work as a proxy taking care to deal with the hash ring in a transparent way.
Check the changed doctests for examples of why it was a bad idea not to sanitize key names and other params. Ignore the changed doctests involving Decimals, I had to change those to get them to pass on my machine but they're not related to me fixes.
Watch out for the Python library though! It doesn't even try to sanitize key names so malformed names cause all sorts of problems (including executing arbitrary commands). Plus unicode strings with non-ascii chars cause it to blow up.
All very easy to fix of course, as soon as I get a chance I'll submit a patch if it hasn't already been done by someone else by then.