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 Linicks
Date Wed, 19 May 2010 20:22:53 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 Linicks.
The comment on this change is: Revised sentance to be more clear..
http://wiki.apache.org/couchdb/Introduction?action=diff&rev1=3&rev2=4

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

  
  == Meet CouchDB  ==
  
- CouchDB is often categorized as a “NoSQL” database, a term that has become increasingly
popular in late 2009, and early 2010.  While this 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 greatly simplifies the maintenance
and development of the database, especially over time when the data  and it's use evolve.
 Additionally, CouchDB doesn't rely on SQL JOINS to merge related data.  This is often a point
of contention with some users of SQL databases, but is generally a non-issue in CouchDB, as
it's powerful Map/Reduce framework comes to the rescue.  
+ CouchDB is often categorized as a “NoSQL” database, a term that has become increasingly
popular in late 2009, and early 2010.  While this 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 greatly simplifies the maintenance
and development of the database, especially over time when the data  and it's 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 it's 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 available.  One of CouchDB's most powerful
feature, is it's replication framework.  This replication framework provides a comprehensive
set of features: 
    * Master → Slave replication
    * Master ↔ Maser replication
    * Filtered Replication
    * Incremental replication with bi-directional conflict detection/resolution
- These replication features can be used in combination to create powerful solutions to many
problems in the IT industry, like reliability, and scalability.  
+ These replication features can be used in combination to create powerful solutions to many
problems in the IT industry, like reliability, and scalability. 
  
  == What it is Not ==
   * A relational database.

Mime
View raw message