Berkeley DB Java Edition
Berkeley DB Java Edition is a high performance transactional storage engine written entirely in Java. Like the highly successful Berkeley DB product, it executes in the address space of the application without the overhead of client/server communication. It stores data in the application's native format, so no runtime data translation is required. It supports full ACID transactions and recovery, and provides an easy-to-use interface, allowing programmers to store and retrieve information quickly, simply, and reliably.
| Tags | Database Database Engines/Servers Software Development Libraries Java Libraries |
|---|---|
| Implementation | Java |
Recent releases
- 05 Nov 2008 18:19
Changes: This release fixes a problem that could cause LogFileNotFoundException in large databases. This could cause data loss, so all users are strongly recommended to upgrade. This problem is found in all prior releases. The bug can occur only for databases with a Btree that is 4 or more levels deep. For the default maximum entries per Btree node (128), this means the database must have grown to at least 10 million records to be a candidate for occurrence of this problem. This is only an approximation, and may be larger or smaller if DatabaseConfig.setNodeMaxEntries has been called.
- 29 Sep 2006 10:55
Changes: Direct Persistence Layer (DPL) is an EJB-style API using Java annotations to dramatically reduce development time, ease schema design, and provide indexed access to objects improving data access times. Schema Evolution of DPL Classes: POJO data contained in Berkeley DB Java Edition using the DPL can now evolve gracefully from version to version.
- 21 Jun 2005 10:22
Changes: Support for JTA, JCA, and JMX. Cleaner enhancements improve out of cache performance. The ability to manage data sets much larger than than the cache is vastly improved in this release. Sequences are now supported. The ability to relax the 'I' (isolation) in 'ACID' transactions is provided by adding support for read committed (sometimes called degree 2) isolation. This complements the existing ability to relax the 'D' (durability) constraints in favor of speed. These are design trade-offs left to the developer.
- 18 Feb 2005 23:28
Changes: In addition to a number of bugfixes, a change was made to internal latching, which resulted in significant performance improvements in multi-threaded applications.
- 03 Jan 2005 10:44
Changes: A great deal of speed and scalability enhancements were made.
