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

Cloudant: All content tagged as Cloudant in NoSQL databases and polyglot persistence

CouchDB BigCouch: Cloudant Open Sourcing their CouchDB Scaling Project

I’ve covered the Cloudant solution for CouchDB horizontal scalability and mentioned that’s probably the most interesting one for scaling CouchDB. Now Cloudant has open sourced it under the name BigCouch and the code is available on ☞ GitHub.

What does it do? Think of BigCouch as a set of Erlang/OTP applications that allow you to create a cluster of CouchDBs that is distributed across many nodes/servers. Instead of one big honking CouchDB, the result is an elastic data store which is fully CouchDB API-compliant.

[…]

The clustering layer is most closely modeled after Amazon’s Dynamo, with consistent hashing, replication, and quorum for read/write operations. CouchDB view indexing occurs in parallel on each partition, and can achieve impressive speedups as compared to standalone serial indexing.

Let’s see if BigCouch is better than CouchDB with a Riak backend.

Original title and link for this post: CouchDB BigCouch: Cloudant Open Sourcing their CouchDB Scaling Project (published on the NoSQL blog: myNoSQL)

via: http://blog.cloudant.com/cloudant-core-is-open-source


CouchDB: Horizontal Scalability from Cloudant

Even if CouchDB benefits of probably one of the most sophisticated and cool replication mechanisms that doesn’t make it horizontally scalable. I’ve already covered the different solutions for scaling CouchDB, but what Cloudant promises seems to be the missing part:

All of these features — distributed, horizontally scalable, durable, consistent — happen with little or no change required in applications that have been written for CouchDB. A cluster looks just like a stand-alone CouchDB, and API compliance has been our goal from the beginning. Granted, there are a few extra options like overriding quorum constant defaults and there are a few vagaries, like views always performing rereduce due to the views being distributed. But on the whole, the extras in Cloudant are transparent to the application.

Now I’m wondering how Cloudant CouchDB scaling compares with running CouchDB with a Riak backend, Riak offering also a Dynamo-like distributed system.

CouchDB: Horizontal Scalability from Cloudant originally posted on the NoSQL blog: myNoSQL

via: http://blog.cloudant.com/dynamo-and-couchdb-clusters