Re:Redis Virtual Memory: the story and the code
by leej on Wednesday February 03, 2010 @03:59PM
(#1098848)
and that's called Redis
Re:Redis Virtual Memory: the story and the code
by ehsanul on Wednesday February 03, 2010 @04:22PM
(#1098898)
Well, the idea preceded Redis and applies more widely. The advantage of having it the way I mentioned is that any database could be plugged in at the back, just as memcached as no requirements for what method of persistence is used. That makes it attractive for other reasons.
In the same vein, I have an idea about forking memcached and turn it into "memd". Instead of just caching for reads, it would allow writes to be done in memory too, which are asynchronously synced to disk when an item expires, or based on certain conditions (I'm thinking based on both time since last updated, and when enough updates are made). Now obviously, this only works if the data you store isn't all that important, which is probably the case for most web applications.