Maybe redis wasn't the best idea...

[spratt]

Reading up on redis, it seems that it is fast specifically because it keeps the whole DB in memory at once...which means there's a cap on DB size. So either we need to expire code (bleh), or we should switch to another db.

[bheesham]

We can maybe try out Riak

[bheesham]

And, it does say so in the introduction to Redis.

[spratt]

1. We all know how much of the docs I read before I wrote the redis port.
2. The relevant part I see is "Redis works with an in-memory dataset," which is true for all databases. There is a dataset that is in-memory, and then there is the full dataset. Redis is designed for the whole dataset to be in-memory. We could continue using it as a cache.

[spratt]

I'm really going to miss Redis' data structures.

[spratt]

This was the article I was reading recently: http://kkovacs.eu/cassandra-vs-mongodb-vs-couchdb-vs-redis

[spratt]

It also considers Riak.

[spratt]

After Redis, I like the sound of:

1. CouchDB: "For accumulating, occasionally changing data, on which pre-defined queries are to be run."
2. Riak: (no quote specifically for our app)

I would like MongoDB for 3, but an empty DB takes up 192Mb??

[spratt]

Riak seems to be designed for fault tolerance, which I'm not super worried about for our app right now? Maybe that would be a better selling feature for @asomayaji's suggested use case.

[bheesham]

I'm indifferent. I say we should just make ports for each, and figure out which one works the best for us. They all look like good alternatives.

[spratt]

That sounds like fun. I suspect Couch and Riak are super similar.

[psimonyi]

If it weren't a shared host, we could just have ridiculous swap...