When to Redis

Post by silentbicycle » Thu, Oct 29, 2009, 8:16 PM UTC

tptacek wrote: post #9

There was a post earlier in the week about why Redis was "awesome" and a "lifestyle" and I posted a kind of snarky comment about why posts like that scare me away from Redis. After this post, I had an hourlong discussion with my lead dev on swapping out memcached for Redis so we could use it for our job scheduler. This post makes an excellent, compelling case for Redis. Just an interesting example of how two differen…

Post by almost » Fri, Oct 30, 2009, 10:53 AM UTC

bham wrote: post #12

almost wrote: post #3

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…

Please submit a few reproducible cases to the mailing list. I'm sure Ludo or I (or you) could even patch it quickly. Thanks!

Post by janl » Sat, Oct 31, 2009, 11:50 AM UTC

silentbicycle wrote: post #11

tptacek wrote: post #9

There was a post earlier in the week about why Redis was "awesome" and a "lifestyle" and I posted a kind of snarky comment about why posts like that scare me away from Redis. After this post, I had an hourlong discussion with my lead dev on swapping out memcached for Redis so we could use it for our job scheduler. This post makes an excellent, compelling case for Redis. Just an interesting example of how two differen…

Indeed. I went to a CouchDB presentation at a local conference, and afterward I asked about some transaction-related details. The presenter didn't understand, but kept repeating that the technology behind it was "way sexy". It was useless and off-putting.