Now Reading
Top NoSQL Key Value Store Databases

Top NoSQL Key Value Store Databases

by Bigdata DeskAugust 9, 2014
Top NoSQL Key Value Store Databases
5 (100%) 14 votes

Top NoSQL Key Value Store Databases : All those databases which are modeled in means other than the tabular relations used in relational databases are known as NO SQL databases. The data structure in key-value database differs from the RDBMS, and therefore some operations are faster in NoSQL and some in RDBMS. Key Value Store databases are classified as Key-Value Store eventually-consistent and Key Value Store ordered databases.

Couchbase, MemcacheDB, Scalaris, DovetailDB, Amazon DynamoDB, MotionDb , Voldemort, FoundationDB, LightCloud, Tokyo Tyrant, Riak, Aerospike and Redis are some of the top No SQL Key Value Store Databases in no particular order.

Top No SQL Key Value Store Databases

Top NoSQL Key Value Store Databases

Top NoSQL Key Value Store Databases


Couchbase Server is an open source, distributed shared nothing architecture, NoSQL document-oriented database. Couchbase is optimized for interactive applications. Couchbase is designed to provide easy to scale key value or document access with low latency and high sustained throughput.



MemcacheDB is a persistence enabled variant of memcached, a general purpose distributed memory caching system often used to speed up dynamic database driven websites by caching data and objects in memory.



Scalaris is a scalable, transactional, distributed key value store. It was the first NoSQL database, that supported the ACID properties for multi key transactions. It can be used for building scalable Web 2.0 services. Scalaris uses a structured overlay with a non blocking Paxos commit protocol for transaction processing with strong consistency over replicas.



DovetailDB is a schemaless, JSON-based database. The principal features include a general purpose indexing strategy that can efficiently handle many types of queries: equality, inequality, and range constraints over boolean combinations of arbitrary fields.


5.Amazon DynamoDB

Amazon DynamoDB is a fully managed proprietary NoSQL database service that is offered by as part of the Amazon Web Services portfolio. DynamoDB exposes a similar data model and derives its name from Dynamo, but has a different underlying implementation. Dynamo had a multi master design requiring the client to resolve version conflicts and DynamoDB use synchronous replication across multiple datacenters.



MotionDb is a Distributed key value storage based on Tokyocabinet.



Voldemort is a distributed data store that is designed as a key-value store used by LinkedIn for high scalability storage.



FoundationDB is a NoSQL database with a shared nothing architecture.The product is designed around a core database, with additional features supplied in layers. The core database exposes an ordered key-value store with transactions.



LightCloud is built on Tokyo Tyrant and is one of the fastest key value databases.


10.Tokyo Tyrant

Tokyo Tyrant is a package of network interface to the DBM called Tokyo Cabinet.

Tokyo Cabinet


Riak is a distributed NoSQL key value data store that offers extremely high availability, fault tolerance, operational simplicity and scalability. In addition to the open-source version, it comes in a supported enterprise version and a cloud storage version that is ideal for cloud computing environments.



Aerospike is optimized for flash with a hybrid RAM/flash storage architecture. Aerospike is claimed as the first NoSQL database to combine transactions with “hot” analytics and the first in-memory NoSQL database with strong consistency (ACID).


13.Redis Labs

Redis Labs is a provider of cloud database services, which provides hosted cloud versions of the popular NoSQL open source databases, Redis and Memcached. Redis is an open-source, networked, in-memory, key-value data store with optional durability. Memcached is a general-purpose distributed memory caching system.

Redis Labs


1 Reviews
  • August 12, 2014 at 4:43 am

    Another KV list without mentioning Redis… I’d love to understand how the writer did research and still managed to avoid a reference to it 🙂

About The Author
Bigdata Desk