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
Tuesday, 27 July 2010
‹ Back

Post 1.0 CouchDB Roadmap

About:
,

Even if CouchDB reached recently its 1.0 release, that doesn’t mean it is feature complete. Mathias Meyer[1] has put together a list of 10 things that should be improved in CouchDB:

  • views are updated on read access
  • no automatic compaction
  • no partial updates
  • no built-in way to scale up[2]
  • pagination is awkward
  • range queries are awkward
  • no CommonJS available in MapReduce functions
  • all reads go to disk (i.e. no caching)
  • unhelpful error messages

CouchDB core developer and Couchio co-founder, Jan Lehnardt’s reaction is encouraging though:

Great roadmap for us! :)

  1. Not so long ago, I published a conversation with Mathias Meyer on getting started with NoSQL  (↩)
  2. To deal with this same feeling, I’ve published a detailed scaling CouchDB article  (↩)

via: http://www.paperplanes.de/2010/7/26/10_annoying_things_about_couchdb.html