Anti-RDBMS: A list of distributed key-value stores
Wednesday, August 5, 2009 at 12:49AM Update 8: Introducing MongoDB by Eliot Horowit.
Update 7: The Future of Scalable Databases by Robin Mathew.
Update 6: NoSQL : If Only it Was that Easy. BJ Clark lays down the law on which databases are scalable: Tokyo - NO, Redis - NO, Voldemort - YES, MongoDB - Not Yet, Cassandra - Probably, Amazon S3 - YES * 2, MySQL - NO. The real thing to point out is that if you are being held back from making something super awesome because you can’t choose a database, you are doing it wrong.
Update 5: Exciting stuff happening in Japan at this Key-Value Storage meeting in Tokyo. Presentations on Groonga, Senna, Lux IO, Tokyo-Cabinet, Tx, repcached, Kai, Cagra, kumofs, ROMA, and Flare.
Update 4: NoSQL and the Relational Model: don’t throw the baby out with the bathwater by Matthew Willson. So my key point is, this kind of modelling is WORTH DOING, regardless of which database tool you end up using for physical storage.
Update 3: Choosing a non-relational database; why we migrated from MySQL to MongoDB. An illuminating article explaining why Boxed Ice move to MongoDB over MySQL and other NoSQL options: easy install, PHP support, replication and master-master support, good doc, auto sharding on the road map. They still use MySQL for billing.
Update 2: They are now called NoSQL databases. So keep up! Eric Lai wrote a good article in Computerworld No to SQL? Anti-database movement gains steam about the phenomena. There was even a NoSQL conference. It was unfortunately full by the time I wanted to sign up, but there are presentations by all the major players. Nice Hacker News thread too.
Update: Some Notes on Distributed Key Stores by Leonard Lin. What's the best way to handle a fast growing system with 100M items that requires low latency and lots of inserts? Leanord takes a trip through several competing systems. The winner was: Tokyo Cabinet.
Richard Jones has put together a very nice list of various key-value stores around the internets. The list includes: Project Voldemort, Ringo, Scalaris, Kai, Dynomite, MemcacheDB, ThruDB, CouchDB, Cassandra, HBase, and Hypertable. Richard also includes some commentary and their basic components (language, fault tolerance, persistence, client protocol, data model, docs, community).
There's an excellent discussion in the comments of Paxos vs Vector Clock techniques for synchronizing writes in the face of network failures.
Reader Comments (5)
Have been enjoying your site and the key-value/#nosql articles.
As an old hand relational dude (oops, there went future employment prospects, I'm wary of tossing the RDMS model, but it is undeniably interesting to keep up with new developments.
Todd
I was wondering how do you see the relationship between In Memory Data Grid and Key-Value stores?
For those who are not familiar with the subject I'll suggest reading one of Todd's articles:
http://highscalability.com/are-cloud-based-memory-architectures-next-big-thing">Are Cloud Based Memory Architectures the Next Big Thing?
Nati S.
You could implement some persistent client-side hashing and you are done.
For Tokyo Tyrant you could also use http://opensource.plurk.com/LightCloud/
Has somebody tried it? Looks quite good.
Excuse me? was that The Future of Scalable Databases by Robin Mathew. I thought i just wrote the article?
Ajatus, I am everywhere :-)