[Zodb-checkins] CVS: ZODB3/Doc - storages.html:1.9

Paul Winkler pw_lists at slinkp.com
Tue Feb 3 11:38:29 EST 2004


Update of /cvs-repository/ZODB3/Doc
In directory cvs.zope.org:/tmp/cvs-serv3898

Modified Files:
	storages.html 
Log Message:

- Added APE comments from Shane
- removed spurious semicolons that broke the stylesheet w/ mozilla


=== ZODB3/Doc/storages.html 1.8 => 1.9 ===
--- ZODB3/Doc/storages.html:1.8	Thu Jun 26 06:14:04 2003
+++ ZODB3/Doc/storages.html	Tue Feb  3 11:38:27 2004
@@ -1,44 +1,64 @@
 <html>
-<body>
-
-<p>This is a feature matrix and comparison of the various ZODB storages.</p>
-
-<p><b>status:</b> Currently it is incomplete. It includes contributions from Toby Dickenson,
-Jeremy Hylton and Barry Warsaw.
-Please update the other columns, add new columns, and particularly add new rows if any other
-areas of comparison are important.</p>
+<head>
 
-<p>Please note that this information is for comparison only. The documentation
-for individual storages is likely to contain more detail than is presented here.</p>
+<title>ZODB Storage Comparison Matrix</title>
 
-<style>
+<STYLE type="text/css">
 
 .comparison th {
 text-align: left;
 }
 
+tr {
+vertical-align: top;
+}
+
 .comparison .title {
 background-color: #eee;
 padding-top: 6pt;
-};
+}
 
 .comparison .filestorage {
 background-color: #A8D8F0;
-};
+}
 
 .comparison .dirstorage {
 background-color: #EBD7B9;
-};
+}
 
 .comparison .bdbstorage {
 background-color: #A8AFF0;
-};
+}
 
 .comparison .ape {
 background-color: #8FC877;
-};
+}
+
+.comment {
+font-style: italic;
+background-color: #dddddd;
+}
+
+</STYLE>
+
+</head>
+
+
+<body>
+
+<p>This is a feature matrix and comparison of the various ZODB storages.</p>
+
+<p><b>status:</b> 
+Currently it is incomplete. It includes contributions from Toby
+Dickenson, Shane Hathaway, Jeremy Hylton, Barry Warsaw, and Paul
+Winkler.  Please update the other columns, add new columns, and
+particularly add new rows if any other areas of comparison are
+important.
+</p>
+
+<p>Please note that this information is for comparison only. The documentation
+for individual storages is likely to contain more detail than is presented here.</p>
 
-</style>
 
 <table class="comparison">
 
@@ -106,7 +126,7 @@
 ?
 </td>
 <td class="ape">
-?
+a handful
 </td>
 </tr>
 
@@ -123,7 +143,7 @@
 2
 </td>
 <td class="ape">
-1?
+1-2
 </td>
 </tr>
 
@@ -158,7 +178,7 @@
 Unix. Should work on Windows with a manual install.
 </td>
 <td class="ape">
-?
+Everywhere.
 </td>
 </tr>
 
@@ -176,7 +196,7 @@
 yes
 </td>
 <td class="ape">
-?
+yes
 </td>
 </tr>
 
@@ -194,7 +214,7 @@
 yes
 </td>
 <td class="ape">
-?
+not yet
 </td>
 </tr>
 
@@ -207,7 +227,7 @@
 </td>
 <td class="dirstorage">
 ZEO 2 and later
-</td>
+</td> 
 <td class="bdbstorage">
 yes
 </td>
@@ -233,7 +253,11 @@
 Some tables are reference counted, with reference counts stored in other tables.
 </td>
 <td class="ape">
-?
+Serializes and stores objects using components.  By writing or
+configuring components, you can store ZODB objects in virtually any
+kind of database.  Alternatively, you can use one of the default
+configurations to store objects on the filesystem, in PostgreSQL, or
+in MySQL.
 </td>
 </tr>
 
@@ -275,7 +299,7 @@
 ZODB4's MemoryStorage is built on the BDBStorage code, with an in-memory compatibility layer to the bsddb module API.
 </td>
 <td class="ape">
-?
+Filesystem storage, relational storage, and custom storage.
 </td>
 </tr>
 
@@ -295,7 +319,7 @@
 Sleepycat's Berkeley DB 4.0.14 and Robin Dunn's PyBSDDB Python bindings.
 </td>
 <td class="ape">
-?
+None.
 </td>
 </tr>
 
@@ -313,7 +337,7 @@
 Yes, in Full variant.
 </td>
 <td class="ape">
-?
+Not currently.
 </td>
 </tr>
 
@@ -330,7 +354,7 @@
 Yes, in Full variant.
 </td>
 <td class="ape">
-?
+No.
 </td>
 </tr>
 
@@ -348,7 +372,7 @@
 A little slower than FileStorage, but not enough to be significant except in a benchmark.
 </td>
 <td class="ape">
-?
+Depends on the component configuration.
 </td>
 </tr>
 
@@ -367,7 +391,7 @@
 Small, and independant of storage size. BerkeleyDB provides many ways to tune how memory is used for caching.
 </td>
 <td class="ape">
-?
+Independent of storage size.
 </td>
 </tr>
 
@@ -386,7 +410,7 @@
 ?
 </td>
 <td class="ape">
-?
+Depends on the component configuration.
 </td>
 </tr>
 
@@ -410,7 +434,9 @@
 Minimal just for cycles. This packing can be performed automatically.
 </td>
 <td class="ape">
-?
+Not needed when storing on the filesystem, but relational 
+databases will need some kind of packing or reference counting.
+
 </td>
 </tr>
 
@@ -434,12 +460,18 @@
 Yes, as BerkeleyDB.
 </td>
 <td class="ape">
-?
+Expected to be provided by the database.
 </td>
 </tr>
 
 <tr><th colspan=4 class=title>Online Replication</th></tr>
 
+<tr><td colspan=4 class=comment>
+Note that it is possible to implement real-time replication, regardless
+of storage, using ZRS. ZRS has only been tested extensively
+with FileStorage.
+</td></tr>
+
 <tr>
 <td class="filestorage">
 No.
@@ -452,10 +484,11 @@
 No. 
 </td>
 <td class="ape">
-?
+No.  
 </td>
 </tr>
 
+
 <tr><th colspan=4 class=title>Storage Checking Tools</th></tr>
 
 <tr>
@@ -470,7 +503,7 @@
 BerkelyDB provides tools for checking the tables, but there is no way to check storage-level details.
 </td>
 <td class="ape">
-?
+Depends on the database.  No extra tools.
 </td>
 </tr>
 
@@ -488,7 +521,7 @@
 No (?)
 </td>
 <td class="ape">
-?
+None needed.  The data is not encoded.
 </td>
 </tr>
 
@@ -507,7 +540,7 @@
 Small, and independant of storage size.
 </td>
 <td class="ape">
-?
+Small, and independant of storage size.
 </td>
 </tr>
 
@@ -527,7 +560,7 @@
 Automatically deletes any partial transactions.
 </td>
 <td class="ape">
-?
+Expected to be provided by the database.
 </td>
 </tr>
 
@@ -548,7 +581,7 @@
 ?
 </td>
 <td class="ape">
-?
+Depends on the database.
 </td>
 </tr>
 
@@ -567,7 +600,7 @@
 As Berkeley DB. Learn the sleepycat tools.
 </td>
 <td class="ape">
-?
+You are expected to know your database.
 </td>
 </tr>
 
@@ -608,7 +641,10 @@
 None
 </td>
 <td class="ape">
-?
+Ape component configurations are reusable for purposes 
+other than persistent data storage.  You can use them for exporting, 
+importing, merging, synchronizing, and versioning objects.  Ape also has 
+a lot of functionality that does not depend on ZODB.
 </td>
 </tr>
 
@@ -626,7 +662,9 @@
 None
 </td>
 <td class="ape">
-?
+It is not yet easy to configure components.  Also, when storing data
+on the filesystem, Ape doesn't yet poll the filesystem for changes to
+cached objects.
 </td>
 </tr>
 




More information about the Zodb-checkins mailing list