NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter



Top 5 Reasons to choose CouchDB

From Bocoup’s Hack Night:

  • CouchDB Stores Data in Documents - CouchDB manages data in the form of JSON documents.
  • Data is Unique and Never Overwritten - when a piece of data is written to a CouchDB document, it will have completely unique identification and will never be overwritten.
  • CouchDB Makes Replication Easy and Efficient - CouchDB databases can replicate from one to another, in a sort of “Master-Master” configuration.  This way, any CouchDB database can accept data as well as replicate that data to any other CouchDB database quickly.
  • Interact With CouchDB Over HTTP Using RESTful - the protocol of CouchDB is RESTful over HTTP.
  • CouchDB Has Own Webserver - Anyone who has messed around with an LAMP system knows that Apache can hog a ton of memory.  Since CouchDB uses has it’s own webserver, you can save a lot of memory by avoiding Apache all together.

Now, the rest of the question is: what are the top 5 reasons for not being able to use CouchDB? Would it be what has been suggested as post 1.0 roadmap and these CouchDB limitations?

Original title and link: Top 5 Reasons to choose CouchDB (NoSQL databases © myNoSQL)