LevelDB: A Fast Persistent Key-Value Store
google-opensource.blogspot.com
LevelDB: A Fast Persistent Key-Value Store
1–10 of 66 posts
The inventors being Jeff Dean and Sanjay Ghemawat.
More here : https://plus.google.com/118227548810368513262/posts/1UEtSkKp1vv
Re: LevelDB: A Fast Persistent Key-Value Store
#2how is this different from membase?
Re: LevelDB: A Fast Persistent Key-Value Store
#3how is this different from membase?
Uhm shouldn't that be ovious by reading the high level descriptions of each? They are for completely different use cases. Membase is a distributed Key/Value server and LevelDB is a Key/Value library.
Re: LevelDB: A Fast Persistent Key-Value Store
#4Re: LevelDB: A Fast Persistent Key-Value Store
#5See also:
Previous discussion - http://news.ycombinator.com/item?id=2526032
Benchmarks vs Kyoto TreeDB and SQLite3 - http://leveldb.googlecode.com/svn/trunk/doc/benchmark.html (discussion - http://news.ycombinator.com/item?id=2813061)
Benchmarks vs InnoDB - http://blog.basho.com/2011/07/01/Leveling-the-Field/
Re: LevelDB: A Fast Persistent Key-Value Store
#6Open sourced as of March 18th, 2011:
http://code.google.com/p/leveldb/source/browse/trunk/LICENSE...
That initial checkin: http://code.google.com/p/leveldb/source/detail?r=2
Re: LevelDB: A Fast Persistent Key-Value Store
#7how is this different from membase?
About like the difference between mysql and sqlite.
Re: LevelDB: A Fast Persistent Key-Value Store
#8Note to myself : Search before you post. Apologies, I checked new and front page only!
Re: LevelDB: A Fast Persistent Key-Value Store
#9Hi there! I'm a YC alum (reMail W09) and helped Jeff and Sanjay with LevelDB. Let me know if you have any questions about LevelDB and I'll see if I can help.
Re: LevelDB: A Fast Persistent Key-Value Store
#10Open sourced as of March 18th, 2011: http://code.google.com/p/leveldb/source/browse/trunk/LICENSE... That initial checkin: http://code.google.com/p/leveldb/source/detail?r=2
Yes, we put up the Google Code site incognito mode back then, but have since added a number of bugfixes and optimizations, so we're actually comfortable announcing the project now.