Re:LevelDB: a fast and lightweight key/value database library
by necubi on Sunday May 08, 2011 @12:34PM
(#2526188)
Note that this is not a database server, like Redis or Memcached. This is a database library, more along the lines of sqlite. In particular: "There is no client-server support builtin to the library. An application that needs such support will have to wrap their own server around the library" and only one process can access a database a time.
[ Parent
| on HN ]
Re:LevelDB: a fast and lightweight key/value database library
by rb2k_ on Sunday May 08, 2011 @01:20PM
(#2526295)
It's the same model that Tokyo/Kyoto Cabinet uses. The difference is that Tokyo/Kyoto Tyrant is an available network interface :)
Re:LevelDB: a fast and lightweight key/value database library
by yingfeng on Sunday May 08, 2011 @11:51PM
(#2527492)
LevelDB should not be compared with the storage model of TC, because leveldb could be looked on a bigtable that run on single node, which is a model that is optimzied for updating instead of reading. The application situation for leveldb is different with that of TC
Re:LevelDB: a fast and lightweight key/value database library
by amjith on Sunday May 08, 2011 @02:40PM
(#2526456)
Hi Thank you for this explanation. My first thought was how is it different than Redis and then when I read no client-server support, I thought, this is worse than Redis. But then your comparison with sqlite makes it a little bit better. I can see a few use cases for it now. Thanks!
Re:LevelDB: a fast and lightweight key/value database library
by rajasharan on Monday May 09, 2011 @05:39PM
(#2530322)
I think saying it's not like 'Memcached' could be wrong. I can think of Memcached as a specialized case of LevelDB.