Redis and SQLite: Why wait for good enough?

Re:Redis and SQLite: Why wait for good enough? by rapind on Thursday February 03, 2011 @08:47AM (#2174665)

I couldn't agree more. One situation I'm using redis for is loads of writes (fast ones) from a rails app.

Because this data adds up and I later need to query / report on it, I'm taking it out of redis after it reaches a certain age (every night) and bulk inserting (archiving) it into postgresql with a bit of aggregation. This gives me the advantage of super fast writes using redis, but also super fast SQL queries for reports that don't have to be real time.

This is probably more hassle than you want to deal with for most situations, but when you do need those fast writes, and you're not super concerned if you lose some data if the server craps out, it seems to be a nice fit.

I'm very happy with the performance so far.

[ Parent | on HN ]

Re:Redis and SQLite: Why wait for good enough? by klochner on Thursday February 03, 2011 @01:44PM (#2176051)

Funny - I use amazon simpleDB/RDS in the exact same way - the index on RDS makes insertion really slow, so I use simpleDB as a cache and load into RDS nightly.

[ Parent | on HN ]

Re:Redis and SQLite: Why wait for good enough? by rapind on Thursday February 03, 2011 @04:43PM (#2177013)

Interesting. How's your write speed with SimpleDB?

[ Parent | on HN ]

Re:Redis and SQLite: Why wait for good enough? by klochner on Thursday February 03, 2011 @06:32PM (#2177499)

the connection time makes it relatively slow (on the order of a few milliseconds), but you can write to multiple keys at once, and/or multithread your client.

[ Parent | on HN ]