News for hackers. Stuff that matters.
Re:LevelDB: A Fast Persistent Key-Value Store by mumrah on Wednesday July 27, 2011 @06:15PM (#2814461)
Anyone know how LevelDB compares to Voldemort? From a cursory glance, they are identical in their simple API (get, put, delete)
Re:LevelDB: A Fast Persistent Key-Value Store by strlen on Thursday July 28, 2011 @01:02AM (#2815463)
Voldemort developer here--

Voldemort to LevelDB is what MySQL is to InnoDB: Voldemort is a distributed system that allows multiple engines to be plugged in. Mostly commonly, companies use either BerkeleyDB or MySQL as a storage engine. LinkedIn, Mendeley, EBay and others also use the read only storage engine, where the data is pre-built in Hadoop and loaded into Voldemort.

I am really excited about LevelDB: while there are higher priority projects on my plate right now, we'd very much like to see a LevelDB storage engine. If anyone is interested in contributing one, they're welcome.

The steps are:

1) Creating JNI bindings to LevelDB (or creating a .so version of LevelDB and creating JNA bindings)

2) Implementing the StorageEngine interface with the bindings, including passing in any configuration.

Here is an example of a third party InnoDB/Haildb storage engine for Voldemort:

https://github.com/sunnygleason/v-storage-haildb

Re:LevelDB: A Fast Persistent Key-Value Store by gaborcselle on Wednesday July 27, 2011 @07:02PM (#2814640)
My understanding is that Voldemort is a distributed key-value storage system, while LevelDB is a local on-disk key-value storage system.