ALL COVERED TOPICS

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

NAVIGATE MAIN CATEGORIES

Close

A Plan for Apache CouchDB: Putting the Apache Back Into CouchDB

Dave Cottlehuber has a great plan for the Apache CouchDB community to restore confidence and increase mind-share in order to fulfil a great goal:

I’d like to see CouchDB as being the enabler in open data, in breaking open the web for joe & jane user, and enabling interoperability of large data sets especially in research and for government. And an independent replication protocol, with a reference implementation, well supported and documented, is critical to that end - even if the back end isn’t actually CouchDB.

I’ve lost track of how many times I wrote that CouchDB needs clarity in positioning and just a bit of an ecosystem (that includes at least good documentation and a set of recommended libraries and tools).

Original title and link: A Plan for Apache CouchDB: Putting the Apache Back Into CouchDB (NoSQL database©myNoSQL)

via: http://muse.net.nz/blog/2012/02/04/putting-the-apache-back-into-couchdb/