Overview

CouchDB is often categorized as a “NoSQL” database. While this term is a rather generic characterization of a database, or data store, it does clearly define a break from traditional SQL-based databases. A CouchDB database lacks a schema, or rigid pre-defined data structures such as tables. Data stored in CouchDB is a JSON document(s). The structure of the data, or document(s), can change dynamically to accommodate evolving needs.

What it is Not

To better understand what CouchDB is, it may be helpful to understand a few things that CouchDB isn’t:

  • A relational database
  • A replacement for all databases.
  • An object-oriented database. While CouchDB stores JSON objects, it isn’t meant to function as a seamless persistence layer for an object-oriented programming language.

Key Characteristics

Let’s review some of the basic elements of CouchDB.

– Documents

A CouchDB document is a JSON object that consists of named fields. A CouchDB database is a flat collection of these documents. Each document is identified by a unique ID.

– Views

Views are the method of aggregating and reporting on the documents in a database, and are built on-demand to aggregate, join and report on database documents. Views are built dynamically and don’t affect the underlying document; you can have as many different view representations of the same data as you like.

– Schema-Free

CouchDB is designed to store and report on large amounts of semi-structured, document oriented data. CouchDB greatly simplifies the development of document oriented applications.
With CouchDB, no schema is required, so new document types with new meaning can be safely added alongside the old.

– Distributed

CouchDB is a peer based distributed database system. Any number of CouchDB hosts (servers and offline-clients) can have independent “replica copies” of the same database.
CouchDB has built-in conflict detection and management and the replication process is incremental and fast, copying only documents changed since the previous replication, the replication in CouchDB is the result of careful ground-up design, engineering and integration. This replication framework provides a comprehensive set of features:

  • Master → Slave replication
  • Master ↔ Master replication
  • Filtered Replication
  • Incremental and bi-directional replication
  • Conflict management


Uses case for CouchDB

There are several use cases that are good uses of CouchDB and other NoSQL repositories. A few that come to mind are:

  • Synchronizing data in an occasionally connected solution. This makes sense in industries like finance where data manipulation or forecasting is done in a disconnected state and synchronized with a server.
  • High velocity log writes
  • High performance caching

Interesting links:

http://www.4tic.com/blog/2011/06/29/couchdb-una-base-de-datos-diferente/

http://guide.couchdb.org/editions/1/en/index.html

http://guide.couchdb.org/

http://couchdb.apache.org/

http://mpouttuclarke.wordpress.com/2011/01/04/couchdb-and-hadoop/

http://www.rubencaceres.com/proyecto/couchdb-y-couchapp-instalacion-y-primeros-pasos
http://www.slideshare.net/jjmerelo/computacin-voluntaria-con-couchdb

http://wiki.apache.org/couchdb/Basics

http://en.wikipedia.org/wiki/CouchDB

http://stackoverflow.com/questions/1307100/when-to-use-couchdb-vs-rdbms

http://www.quora.com/CouchDB/What-are-the-best-use-cases-for-CouchDB

http://guide.couchdb.org/draft/performance.html

facebooktwittergoogle_plusredditlinkedinby feather

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>