Live data from Hacker News

The Redis criticism thread

antirez.com

1–10 of 47 posts

Re: The Redis criticism thread

#3
There has been a lot of constructive discussion in the Google Groups thread, and a lot of negativity on the same topic on Twitter. Ignoring for the moment the difference in discussion platforms, I am uncertain why the sudden uptick in Redis negativity.

Is it from users trying (and failing) to replace RDBMS or distributed platforms feature-for-feature with a single threaded, memory limited store like Redis? Or could it be FUD from people interested in seeing their new platform-du-jour get more attention?

Re: The Redis criticism thread

#5
This is the first time I've ever heard any criticism for redis. As far as I know, everyone loves it, it's a great tool for many jobs and it's amazingly written and solid to boot. I think many of the critics are trying to apply it in ways it wasn't meant to be used.

As far as I know, its main purpose is non-critical data that needs to be accessed as quickly as possible in various different ways, and that's where redis shines.

Re: The Redis criticism thread

#7
post #5

This is the first time I've ever heard any criticism for redis. As far as I know, everyone loves it, it's a great tool for many jobs and it's amazingly written and solid to boot. I think many of the critics are trying to apply it in ways it wasn't meant to be used. As far as I know, its main purpose is non-critical data that needs to be accessed as quickly as possible in various different ways, and that's where redis…

I don't pay super close attention to this stuff, but it's very obvious to me that not everyone likes Redis; in particular, the kinds of people who have problems with Mongodb tend also to have the same problems with Redis; long-term operational reliability is a big question mark with it.

For my part: on only a few occasions (mostly fuzzer farm stuff) have I ever used Redis and been happy with the decision. I usually regret using it. I always regret using it as an alternative to SQL.

Re: The Redis criticism thread

#8
post #5

This is the first time I've ever heard any criticism for redis. As far as I know, everyone loves it, it's a great tool for many jobs and it's amazingly written and solid to boot. I think many of the critics are trying to apply it in ways it wasn't meant to be used. As far as I know, its main purpose is non-critical data that needs to be accessed as quickly as possible in various different ways, and that's where redis…

It would be great to also enumerate other examples where it shines.

I've used it for caching, session and transient objects connected to Rails without issue for the last two years.

Additionally, I've been looking at it recently for a simple database to perform fast matches on sorted data (E.g. get me the lowest number in this set).

Re: The Redis criticism thread

#9
post #7
post #5

This is the first time I've ever heard any criticism for redis. As far as I know, everyone loves it, it's a great tool for many jobs and it's amazingly written and solid to boot. I think many of the critics are trying to apply it in ways it wasn't meant to be used. As far as I know, its main purpose is non-critical data that needs to be accessed as quickly as possible in various different ways, and that's where redis…

I don't pay super close attention to this stuff, but it's very obvious to me that not everyone likes Redis; in particular, the kinds of people who have problems with Mongodb tend also to have the same problems with Redis; long-term operational reliability is a big question mark with it. For my part: on only a few occasions (mostly fuzzer farm stuff) have I ever used Redis and been happy with the decision. I usually r…

What went wrong? What's the Redis K/V model for it being used as a fuzzer farm data thing?

Re: The Redis criticism thread

#10
post #8
post #5

This is the first time I've ever heard any criticism for redis. As far as I know, everyone loves it, it's a great tool for many jobs and it's amazingly written and solid to boot. I think many of the critics are trying to apply it in ways it wasn't meant to be used. As far as I know, its main purpose is non-critical data that needs to be accessed as quickly as possible in various different ways, and that's where redis…

It would be great to also enumerate other examples where it shines. I've used it for caching, session and transient objects connected to Rails without issue for the last two years. Additionally, I've been looking at it recently for a simple database to perform fast matches on sorted data (E.g. get me the lowest number in this set).

For three years we've been using it as message bus, statistics tracker, and storing medium-term data (expires after 1 month). We've up/downgraded multiple times without issue.
Post reply on HN