melvin12harmon

Hi all,

I am currently building a prototype using the Java API to Berkeley DB.
I am trying to figure out if switching to the Java Edition is the
right thing to do.

So far I can only come up with two reasons why a Java project wouldn't
use the Java edition:

1) The Java Edition lacks High Availability support

2) The Java Edition only supports a single process, multi-threaded
model, whereas the 'Berkeley DB Transactional Data Store' supports
multi-process access.

Are these both two issues correct? Does anyone have any other issues
to consider?

thanks,
-m

bostic

Those are the major questions. Other possible issues:

3) The Berkeley DB code has more access methods (Java Edition
only has a B+tree variant at the moment, while Berkeley DB
in addition supports Queue, Hash and Recno). Depending on
the application's data needs, that may be relevant. For more
information, see the "Selecting an access method" section of
the Berkeley DB Reference Guide, included in your download
package and also available at:

http://www.sleepycat.com/docs/ref/am_conf/select.html

4) The Berkeley DB code base has been around longer than Java
Edition, so it has additional features: XML, encryption,
XA/RM support, application-specific transactions, bulk-record
retrieval, RPC support, and so on. I think these are less
significant issues, but they're potentially important to
specific applications. Obviously, many of these will be
added to Java Edition as the product moves forward.

Regards,
--keith

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Keith Bostic bostic@sleepycat.com
Sleepycat Software Inc. keithbosticim (ymsgid)
118 Tower Rd. +1-781-259-3139
Lincoln, MA 01773 http://www.sleepycat.com