• Home
  • History
  • Annotate
  • Line#
  • Navigate
  • Raw
  • Download
  • only in /asuswrt-rt-n18u-9.0.0.4.380.2695/release/src/router/db-4.8.30/docs/programmer_reference/
1<?xml version="1.0" encoding="UTF-8" standalone="no"?>
2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml">
4  <head>
5    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
6    <title>The Berkeley DB products</title>
7    <link rel="stylesheet" href="gettingStarted.css" type="text/css" />
8    <meta name="generator" content="DocBook XSL Stylesheets V1.73.2" />
9    <link rel="start" href="index.html" title="Berkeley DB Programmer's Reference Guide" />
10    <link rel="up" href="intro.html" title="Chapter 1.  Introduction" />
11    <link rel="prev" href="intro_where.html" title="Where does Berkeley DB run?" />
12    <link rel="next" href="am_conf.html" title="Chapter 2.  Access Method Configuration" />
13  </head>
14  <body>
15    <div class="navheader">
16      <table width="100%" summary="Navigation header">
17        <tr>
18          <th colspan="3" align="center">The Berkeley DB products</th>
19        </tr>
20        <tr>
21          <td width="20%" align="left"><a accesskey="p" href="intro_where.html">Prev</a> </td>
22          <th width="60%" align="center">Chapter 1. 
23		Introduction
24        </th>
25          <td width="20%" align="right"> <a accesskey="n" href="am_conf.html">Next</a></td>
26        </tr>
27      </table>
28      <hr />
29    </div>
30    <div class="sect1" lang="en" xml:lang="en">
31      <div class="titlepage">
32        <div>
33          <div>
34            <h2 class="title" style="clear: both"><a id="intro_products"></a>The Berkeley DB products</h2>
35          </div>
36        </div>
37      </div>
38      <div class="toc">
39        <dl>
40          <dt>
41            <span class="sect2">
42              <a href="intro_products.html#id1587931">Berkeley DB Data Store</a>
43            </span>
44          </dt>
45          <dt>
46            <span class="sect2">
47              <a href="intro_products.html#id1588210">Berkeley DB Concurrent Data Store</a>
48            </span>
49          </dt>
50          <dt>
51            <span class="sect2">
52              <a href="intro_products.html#id1588893">Berkeley DB Transactional Data Store</a>
53            </span>
54          </dt>
55          <dt>
56            <span class="sect2">
57              <a href="intro_products.html#id1587492">Berkeley DB High Availability</a>
58            </span>
59          </dt>
60        </dl>
61      </div>
62      <p>Oracle licenses four different products that use the Berkeley DB technology.
63Each product offers a distinct level of database support.  It is not
64possible to mix-and-match products, that is, each application or group
65of applications must use the same Berkeley DB product.</p>
66      <p>All four products are included in the single Open Source distribution
67of Berkeley DB from Oracle, and building that distribution automatically
68builds all four products.  Each product adds new interfaces and services
69to the product that precedes it in the list.  As a result, developers
70can download Berkeley DB and build an application that does only single-user,
71read-only database access, and easily add support later for more users
72and more complex database access patterns.</p>
73      <p>Users who distribute Berkeley DB must ensure that they are licensed for the
74Berkeley DB interfaces they use.  Information on licensing is available from
75Oracle.</p>
76      <div class="sect2" lang="en" xml:lang="en">
77        <div class="titlepage">
78          <div>
79            <div>
80              <h3 class="title"><a id="id1587931"></a>Berkeley DB Data Store</h3>
81            </div>
82          </div>
83        </div>
84        <p>The Berkeley DB Data Store product is an embeddable, high-performance data store.  It
85supports multiple concurrent threads of control (including multiple
86processes and multiple threads of control within a process) reading
87information managed by Berkeley DB.  When updates are required, only a single
88thread of control may be using the database.  The Berkeley DB Data Store does no locking,
89and so provides no guarantees of correct behavior if more than one
90thread of control is updating the database at a time.  The Berkeley DB Data Store is
91intended for use in read-only applications or applications which can
92guarantee no more than one thread of control will ever update the
93database at a time.</p>
94      </div>
95      <div class="sect2" lang="en" xml:lang="en">
96        <div class="titlepage">
97          <div>
98            <div>
99              <h3 class="title"><a id="id1588210"></a>Berkeley DB Concurrent Data Store</h3>
100            </div>
101          </div>
102        </div>
103        <p>The Berkeley DB Concurrent Data Store product adds multiple-reader, single writer capabilities to
104the Berkeley DB Data Store product, supporting applications that need concurrent updates
105and do not want to implement their own locking protocols.  Berkeley DB Concurrent Data Store is
106intended for applications that require occasional write access to a
107database that is largely used for reading.</p>
108      </div>
109      <div class="sect2" lang="en" xml:lang="en">
110        <div class="titlepage">
111          <div>
112            <div>
113              <h3 class="title"><a id="id1588893"></a>Berkeley DB Transactional Data Store</h3>
114            </div>
115          </div>
116        </div>
117        <p>The Berkeley DB Transactional Data Store product adds full transactional support and recoverability
118to the Berkeley DB Data Store product.  Berkeley DB Transactional Data Store is intended for applications that require
119industrial-strength database services, including excellent performance
120under high-concurrency workloads with a mixture of readers and writers,
121the ability to commit or roll back multiple changes to the database at
122a single instant, and the guarantee that even in the event of a
123catastrophic system or hardware failure, any committed database changes
124will be preserved.</p>
125      </div>
126      <div class="sect2" lang="en" xml:lang="en">
127        <div class="titlepage">
128          <div>
129            <div>
130              <h3 class="title"><a id="id1587492"></a>Berkeley DB High Availability</h3>
131            </div>
132          </div>
133        </div>
134        <p>The Berkeley DB High Availability product support for data replication.  A single master system
135handles all updates, and distributes them to as many replicas as the
136application requires. All replicas can handle read requests during
137normal processing. If the master system fails for any reason, one of
138the replicas takes over as the new master system, and distributes
139updates to the remaining replicas.</p>
140      </div>
141    </div>
142    <div class="navfooter">
143      <hr />
144      <table width="100%" summary="Navigation footer">
145        <tr>
146          <td width="40%" align="left"><a accesskey="p" href="intro_where.html">Prev</a> </td>
147          <td width="20%" align="center">
148            <a accesskey="u" href="intro.html">Up</a>
149          </td>
150          <td width="40%" align="right"> <a accesskey="n" href="am_conf.html">Next</a></td>
151        </tr>
152        <tr>
153          <td width="40%" align="left" valign="top">Where does Berkeley DB run? </td>
154          <td width="20%" align="center">
155            <a accesskey="h" href="index.html">Home</a>
156          </td>
157          <td width="40%" align="right" valign="top"> Chapter 2. 
158		Access Method Configuration
159        </td>
160        </tr>
161      </table>
162    </div>
163  </body>
164</html>
165