Voldemort is written in Java and was developed by LinkedIn.
It is not a classic relational database, being more close to Redis or FlockDB than to MySQL.
Here are some key features of "Voldemort":
· Data is automatically replicated over multiple servers.
· Data is automatically partitioned so each server contains only a subset of the total data
· Server failure is handled transparently
· Pluggable serialization is supported to allow rich keys and values including lists and tuples with named fields, as well as to integrate with common serialization frameworks like Protocol Buffers, Thrift, Avro and Java Serialization
· Data items are versioned to maximize data integrity in failure scenarios without compromising availability of the system
· Each node is independent of other nodes with no central point of failure or coordination
· Good single node performance: you can expect 10-20k operations per second depending on the machines, the network, the disk system, and the data replication factor
· Support for pluggable data placement strategies to support things like distribution across data centers that are geographically far apart.
· Voldemort combines in memory caching with the storage system so that a separate caching tier is not required (instead the storage system itself is just fast)
· Unlike MySQL replication, both reads and writes scale horizontally
· Data portioning is transparent, and allows for cluster expansion without rebalancing all data
· Data replication and placement is decided by a simple API to be able to accommodate a wide range of application specific strategies
· The storage layer is completely mockable so development and unit testing can be done against a throw-away in-memory storage system without needing a real cluster (or even a real storage system) for simple testing
Find us on Google+
