Keyspace. Yet Another Key-Value Store—this one focuses on high availability, with one server in the cluster serving as master (and handling all writes), and the paxos algorithm handling replication and ensuring a new master can be elected should the existing master become unavailable. Clients can chose to make dirty reads against replicated servers or clean reads by talking directly to the master. Underlying storage is BerkeleyDB, and the authors claim 100,000 writes/second. Released under the AGPL.
Sign in with 
OpenID
Hrm. It's AGPL'd... Does that mean that if I use it my app has to be GPL'd too? Just looked over the license and it's unclear to me.
Mike Malone - 16th July 2009 19:51 - #
Hi, I'm one of the developers.
Short answer is no, your app would not have to be GPL'd.
My intention for choosing the AGPL: The AGPL is about closing the so-called distribution loophole; if you modify the Keyspace source code but don't redistribute it, only use it to serve your eg. PHP app, then under the GPL you would not have to share your Keyspace changes. With the AGPL you have to, but this doesn't affect your eg. PHP code.
Don't worry too much about the AGPL vs. GPL issue.
Marton Trencseni - 17th July 2009 10:21 - #