Oracle Berkeley DB Java Edition

High performance transactional storage engine.
Download

Oracle Berkeley DB Java Edition Ranking & Summary

Advertisement

  • Rating:
  • License:
  • Freeware
  • Price:
  • FREE
  • Publisher Name:
  • ORACLE
  • Publisher web site:
  • http://www.oracle.com/technology/products/jdev/11/index.html
  • Operating Systems:
  • Mac OS X 10.0 or later
  • File Size:
  • 10 MB

Oracle Berkeley DB Java Edition Tags


Oracle Berkeley DB Java Edition Description

High performance transactional storage engine. Oracle Berkeley DB Java Edition is a high performance, transactional storage engine written entirely in Java. Like the highly successful Berkeley DB product, Berkeley DB Java Edition 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. Berkeley DB Java Edition supports full ACID transactions and recovery. It provides an easy-to-use, programmatic interface, allowing developers to store and retrieve information quickly, simply and reliably. Here are some key features of "Oracle Berkeley DB Java Edition": · Local, in-process data storage. · Schema-neutral, application native data storage. · Keyed and sequential data retrieval. · Easy-to-use Java Collections API. · Persistence API for accessing Java objects. · Single process, multi-threading model. · Record level locking for high concurrency. · Support for secondary indexes. · In-memory, on disk or both. · Configurable background cleaner threads re-organize data and optimize disk use. · Full ACID compliance. · Selectable isolation levels and durability guarantees, configurable on a per-transaction basis. · Managed transactions using the Java Transaction API (JTA). · J2EE application server integration using J2EE Connector Architecture(JCA). · Provides support for monitoring, auditing and administration using the Java Management Extensions (JMX). · Catastrophic and routine failure recovery modes. · Timeout based deadlock detection. · Hot and cold backups, log file compaction, and full database dumps. · 100% pure Java for portability and ease of development. · Single JAR file - easy to install, runs in the same JVM as the application. · Java 1.4.2 or later Standard Edition JVM required. · Programmatic administration and management-zero human administration. · API for routine administrative functions. · Small footprint 772KB. · Scalable to terabytes of data, millions of records. · Source code, test suite included. Requirements: · Java 1.5 or later. What's New in This Release: · This release features JE High Availability, which permits the use of JE with replication. See the High Availability Guide for an introduction to the product, and the com.sleepycat.je.rep javadoc for API specifications. · JE now provides two JMX MBean implementations for monitoring a running JE application. A JConsole plugin is also provided for accessing the new JEMonitor and RepJEMonitor classes. Environment statistics can be collected and graphed, and other state information can be perused. See the how-to for more information. · It is critical that invalid files are not added to a backup set, since then both the live environment and the backup will be invalid. Two new classes now support verification of log files prior to making a backup. · The com.sleepycat.je.util.LogVerificationInputStream class enables log verification programmatically as files are being copied. The com.sleepycat.je.util.DbVerifyLog class is a simple command line utility for inclusion in backup scripts. · Cursor and Database record retrieval has been optimized to significantly reduce I/O when DatabaseEntry.setPartial is used to suppress return of the data item and the READ_UNCOMMITTED isolation mode is used. See "Using Partial DatabaseEntry Parameters"in the Cursor javadoc for more information. · The EnvironmentConfig.setNodeName(String nodeName) and EnvironmentConfig.getNodeName() methods have been added to match those same methods in ReplicationConfig. Setting the EnvironmentConfig node name will cause java.util.logging messages and thread names to include the user-specified name. This was previously only true for replicated environments, and has been extended to work for non-replicated environments, as a debugging aid when using multiple environments in the same JVM. The feature was originally requested on the OTN forum. (changed in 4.0.70)


Oracle Berkeley DB Java Edition Related Software