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, 14 September 2010
‹ Back

CouchDB: The File system for the internet

About:
,
,
,

Nitin Borwankar, Couch DB, VP of business development:

the goal here is to make couchdb the file system for the internet

via ☞ Chris Hardcastle

Sometimes I’m getting confused: is CouchDB for mobiles[1], or is CouchDB for scalable bigdata apps[2], or is CouchDB for disconnected web applications, or is CouchDB for Geo applications?

While I’m not saying that it should do only one thing, the message sounds a bit confusing when compared with other NoSQL databases: Cassandra, HBase: BigData for big boys, Riak: Amazon-style scalable key-value store, Membase: the persistent memcached, Redis: the smart data type, super fast key-value store.

  1. CouchDB for mobiles:  (↩)
  2. CouchDB for BigData:  (↩)

Original title and link for this post: CouchDB: The File system for the internet (published on the NoSQL blog: myNoSQL)