couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Couchdb Wiki] Trivial Update of "Introduction" by TiffanyConroy
Date Sun, 07 Nov 2010 11:41:49 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.

The "Introduction" page has been changed by TiffanyConroy.
The comment on this change is: "scrap that sentence entirely" as per @janl.
http://wiki.apache.org/couchdb/Introduction?action=diff&rev1=7&rev2=8

--------------------------------------------------

  == Meet CouchDB ==
  CouchDB is often categorized as a “NoSQL” database, a term that became increasingly
popular in late 2009, and early 2010.  While this term is a rather generic, and sometimes
offensive, characterization of a database, or data store, it does clearly define a break from
traditional SQL-based databases.  CouchDB makes a clean break from the SQL database world
in many ways.  One of the primary differences  is  the lack of a schema,  or rigid pre-defined
data structures like tables.   Because the data stored in CouchDB is a JSON document(s), the
structure of the data, or document(s), can change dynamically.  This feature greatly simplifies
the maintenance and development of the database, especially over time when the data and its
use evolve.  Additionally, CouchDB doesn't rely on SQL JOINS to merge related data.  This
is often confusing for some users of traditional SQL databases, but is generally a non-issue
once CouchDB users become familiar its powerful Map/Reduce framework.
  
- CouchDB's departure from the SQL world isn't the only thing that makes CouchDB stand out
among a growing list of “NoSQL” databases.  One of CouchDB's most powerful feature, is
its replication framework.  This replication framework provides a comprehensive set of features:
+ One of CouchDB's most powerful feature, is its replication framework.  This replication
framework provides a comprehensive set of features:
  
   * Master → Slave replication
   * Master ↔ Maser replication

Mime
View raw message