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] Update of "Introduction" by RandallLeeds
Date Sun, 25 Dec 2011 23:54:52 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 RandallLeeds:
http://wiki.apache.org/couchdb/Introduction?action=diff&rev1=17&rev2=18

Comment:
Move replication information down to the "Distributed" section. Remove "you" sentence.

  = Introduction =
  == 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 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.
- 
- One of CouchDB's most powerful features is its replication framework.  This replication
framework provides a comprehensive set of features:
- 
-  * Master → Slave replication
-  * Master ↔ Master 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. In addition to the fantastic replication features, CouchDB's
reliability and scalability is further enhanced by being implemented in the Erlang programming
language. Erlang has built-in support for concurrency, distribution, fault tolerance, and
has been used for years to build reliable systems in the telecommunications industry. By design,
the Erlang language and runtime are able to take advantage of newer hardware with multiple
CPU cores. When you look at all of the great characteristics of Erlang, it becomes clear why
CouchDB uses it for its foundation.
  
  == What it is Not ==
  To better understand what CouchDB is, it may be helpful to understand a few things that
CouchDB isn't:
@@ -56, +47 @@

  
  CouchDB has built-in conflict detection and management and the replication process is incremental
and fast, copying only documents changed since the previous replication. Most applications
require no special planning to take advantage of distributed updates and replication.
  
- Unlike cumbersome attempts to bolt distributed features on top of the same legacy models
and databases, replication in CouchDB is the result of careful ground-up design, engineering
and integration. The document, view, security and replication  models, the special purpose
query language, and the robust disk layout are all carefully constructed to produce a reliable
and efficient system.
+ Unlike cumbersome attempts to bolt distributed features on top of the same legacy models
and databases, 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
+ 
+ These replication features can be used in combination to create powerful solutions to many
problems in the IT industry. In addition to the fantastic replication features, CouchDB's
reliability and scalability is further enhanced by being implemented in the Erlang programming
language. Erlang has built-in support for concurrency, distribution, fault tolerance, and
has been used for years to build reliable systems in the telecommunications industry. By design,
the Erlang language and runtime are able to take advantage of newer hardware with multiple
CPU cores.
+ 

Mime
View raw message