Hacker News Reader

Redis is almost perfect for a queue because of it's lists and atomic operations. And, most of all, because it's persistent. It's amazing how many queues aren't persistent.

I'm glad someone finally did this, it could be a great solution. I'm looking forward to digging into this.

View on HN

And, most of all, because it's persistent.

Just a slight caution, since Redis stores it's data in memory and asynchronously writes out to disk it is possible to lose small amounts of data in a crash. In most cases this is an acceptable trade off for the speed of an in-memory database though.

There is also plenty of good info on the project page - http://code.google.com/p/redis/

Since Redis 1.1 (currently in beta - don't use it in production for now) there is a new append-only journal storage system alternative to the main one (that is, snapshotting), so starting from 1.1 Resque will be more reliable as well if needed, because in this new (optional) configuration Redis can't lose data. It's also possible to configure if it should fsync() never, everysec, or after every write. It's up to you to select the tradeoff between speed and safety :)

Fantastic. Redis can go in both my ephemeral and critical systems.

You're a whirlwind of activity.

Exciting stuff maybe we can drop JMS and use this instead

Reply on news.ycombinator.com