News for hackers. Stuff that matters.
Re: Membase: A distributed key-value database for modern web... by StavrosK on Sunday July 11, 2010 @08:02AM (#1505377)
I am baffled by these new trends. I have seen websites that need scalability cache all the DB queries in memcached, but the queries didn't have any large degree of temporal locality. How is this supposed to do anything other than move the database into memory? Shouldn't the DBMS already do that by itself? The only benefit I can see is that the queries would be memoized instead of having to be run again and again, but I'm not sure that would be such a great advantage if the entire DB was loaded in memory.

Anyway, I'm just thinking aloud here, but it seems to me that in many cases you really don't want a caching layer above the DB...

Re: Membase: A distributed key-value database for modern web... by sketerpot on Sunday July 11, 2010 @12:54PM (#1505755)
This one isn't just a cache; it's a database with a simple key-value data model. It has very good clustering support. It can handle datasets too large for memory. It's fast, allegedly easy to set up (I haven't tried it), and you can communicate with it using existing memcached client libraries. I think it sounds like an interesting option.

I also think that, in a few months, Redis will probably have the same nice characteristics of Membase, but with a much nicer set of datatypes. Membase does everything I described right now, though, which is worth something.