Lesson plan

BigCouch

BigCouch is an open-source, highly available, fault-tolerant, clustered & API-compliant version of Apache CouchDB, which was maintained by Cloudant. On January 5, 2012, Cloudant announced they would contribute the BigCouch horizontal scaling framework into the CouchDB project. The merge was completed in July 2013. Cloudant announced in June 2015 that they were no longer supporting BigCouch. BigCouch allows users to create clusters of CouchDBs that are distributed over an arbitrary number of servers. While it appears to the end-user as one CouchDB instance, it is in fact one or more nodes in an elastic cluster, acting in concert to store and retrieve documents, index and serve views, and serve CouchApps. Clusters behave according to concepts outlined in Amazon's Dynamo paper, namely that each node can accept requests, data is placed on partitions based on a consistent hashing algorithm, and quorum protocols are for read/write operations. It relies on Erlang and the Open Telecom Platform, despite using its own RPC mechanism over OTP's own "rex" server. BigCouch was developed to address a common complaint raised by CouchDB skeptics is that "it doesn't scale," by which they mean it does not scale horizontally across many servers. This feature is necessary for CouchDB is to be used to address Big Data problems.

Back to article

Article summary

BigCouch is an open-source, highly available, fault-tolerant, clustered & API-compliant version of Apache CouchDB, which was maintained by Cloudant. On January 5, 2012, Cloudant announced they would contribute the BigCouch horizontal scaling framework into the CouchDB project. The merge was completed in July 2013. Cloudant announced in June 2015 that they were no longer supporting BigCouch. BigCouch allows users to create clusters of CouchDBs that are distributed over an arbitrary number of servers. While it appears to the end-user as one CouchDB instance, it is in fact one or more nodes in an elastic cluster, acting in concert to store and retrieve documents, index and serve views, and serve CouchApps. Clusters behave according to concepts outlined in Amazon's Dynamo paper, namely that each node can accept requests, data is placed on partitions based on a consistent hashing algorithm, and quorum protocols are for read/write operations. It relies on Erlang and the Open Telecom Platform, despite using its own RPC mechanism over OTP's own "rex" server. BigCouch was developed to address a common complaint raised by CouchDB skeptics is that "it doesn't scale," by which they mean it does not scale horizontally across many servers. This feature is necessary for CouchDB is to be used to address Big Data problems.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.