Kumofs is a simple and fast distributed key-value store. You can use a memcached client library to set, get, CAS or delete values from/into kumofs. Backend storage is Tokyo Cabinet and it will give you great performance. Data is partitioned and replicated over multiple servers. Extreme single node performance; comparable with memcached. Both read and write performance got improved as servers added. Servers can be added without stopping the system. Servers can be added without modifying any configuration files. The system does not stop even if one or two servers crashed. The system does not stop to recover crashed servers. Automatic rebalancing support with a consistency control algorithm. Safe CAS operation support. memcached protocol support. Kumofs is used at Nico Nico douga (Wikipedia), the most popular video sharing service in Japan.
Hibari is a distributed, non-relational database management system (distributed non-RDBMS) based on distributed key value store technology, implemented by Gemini Mobile Technologies, it inherits important characteristics of both the distributed non-RDBMS world and of Gemini's HyperScale® Platform.
Hibari has the following characteristics to flexibly support growing volumes of data in cloud computing space. Economic system build-up using commodity hardware Flexible, high scalability High performance and availability by consistent hashing across multiple machines High fault-tolerance by chain replication across multiple machines Safety without a single point of failure (SPOF)
The Apache Cassandra Project develops a highly scalable second-generation distributed database, bringing together Dynamo's fully distributed design and Bigtable's ColumnFamily-based data model.
Cassandra was open sourced by Facebook in 2008, where it was designed by Avinash Lakshman (one of the authors of Dynamo) and Prashant Malik. In a lot of ways you can think of Cassandra as Dynamo 2.0. Cassandra is in production use at Rackspace, Digg, and a number of other companies, but is still under heavy development.
Have you ever wondered how optimized your Memcached installation is? There is a common misconception that one doesn't have to think too deeply about Memcached performance, but that is not true. If your setup is inefficient, you could:
* Burn Memory
* Waste Network Round-Trips
* Store Keys That Never Get Retrieved
* Have a Low Cache Hit Ratio (i.e. query MySQL too much)
* Suffer a fate too horrible to contemplate.Percona does a lot of consulting around Memcached, so we try to take a quantitative, scientific approach to measuring memcached performance, just like everything else we do.
The Tungsten Replicator implements open source database-neutral master/slave replication. Master/slave replication is a highly flexible technology that can solve a wide variety of problems including the following:
* Availability - Failing over to a slave database if your master database dies
* Performance Scaling - Spreading reads across many copies of data
* Cross-Site Clustering - Maintaining active database replicas across WANs
* Change Data Capture - Extracting changes to load data warehouses or update other systems
* Zero Downtime Upgrade - Performing upgrades on a slave server which then becomes the master