summaryrefslogtreecommitdiff
path: root/db/docs/ref/rep/intro.html
diff options
context:
space:
mode:
Diffstat (limited to 'db/docs/ref/rep/intro.html')
-rw-r--r--db/docs/ref/rep/intro.html24
1 files changed, 11 insertions, 13 deletions
diff --git a/db/docs/ref/rep/intro.html b/db/docs/ref/rep/intro.html
index e0d670f98..439937cd1 100644
--- a/db/docs/ref/rep/intro.html
+++ b/db/docs/ref/rep/intro.html
@@ -1,4 +1,4 @@
-<!--Id: intro.so,v 1.2 2001/10/13 20:21:47 bostic Exp -->
+<!--Id: intro.so,v 1.3 2001/10/24 19:06:38 bostic Exp -->
<!--Copyright 1997-2001 by Sleepycat Software, Inc.-->
<!--All rights reserved.-->
<html>
@@ -16,19 +16,17 @@
<p>
<h1 align=center>Introduction</h1>
<p>Berkeley DB includes support for building highly available applications based
-on single-master (read-only) replication. Berkeley DB replication groups
-consist of some number of independently configured database
-environments. The database environments might be on separate computers,
-on separate boards in a computer with replicated hardware, or on
-separate disks in a single computer. The environments may be accessed
-by any number of applications, from one to many. As always with Berkeley DB
+on replication. Berkeley DB replication groups consist of some number of
+independently configured database environments. There is a single
+<i>master</i> database environment and one or more <i>client</i>
+database environments. Master environments support both database reads
+and writes; client environments support only database reads. If the
+master environment fails, applications may upgrade a client to be the
+new master. The database environments might be on separate computers,
+on separate hardware partitions in a non-uniform memory access (NUMA)
+system, or on separate disks in a single server. As always with Berkeley DB
environments, any number of concurrent processes or threads may access
-the database environment.
-<p>Berkeley DB replication groups contain a single <i>master</i> database
-environment and one or more <i>client</i> database environments.
-Master environments support both database reads and writes; client
-environments support only database reads. If the master environment
-fails, applications may upgrade a client to be the new master.
+a database environment.
<p>Applications may be written to provide various degrees of consistency
between the master and clients. The system can be run synchronously
such that replicas are guaranteed to be up-to-date with all committed