BerkeleyDB is only a key-value embedded database, and no application-layer data protocol on top of it(But it provides lots of amazing storage apis!). And also it can not be distributed except you build your own network logic on it. Memcache protocol is very lightweight, and now has a lot of client apis, and also fits the key-value pattern, so Memcachedb was born.
On Sun, Mar 16, 2008 at 12:27 AM, howard chen <[EMAIL PROTECTED]> wrote: > On Sun, Mar 16, 2008 at 12:01 AM, Steve Chu <[EMAIL PROTECTED]> wrote: > > You may check this: http://memcachedb.org/memcachedb-guide-1.0.pdf, > > and almost all my ideas about memcachedb on it, I think maybe you will > > find your answer :p > > > > > > I agree the points in the slides comparing with RDBMS, but how about > compare your project with sleepycat / Berkeley DB except you can use > the existing protocol. > > Howard > -- Steve Chu http://stvchu.org
