Why Java Collections for Berkeley DB?
The Java collections interface was chosen as the best Java API for Berkeley DB given these requirements: • provide the Java developer with an API that is as familiar and easy to use as possible • provide access to all, or a large majority, of the features of the underlying Berkeley DB storage system • compared to the Berkeley DB API, provide a higher-level API that is oriented toward Java developers • for ease of use, support object-to-data bindings, per-thread transactions, and some traditional database features such as foreign keys • provide a thin layer that can be thoroughly tested and which does not significantly impact the reliability and performance of Berkeley DB Admittedly there are several things about the Java Collections API that don’t quite fit with Berkeley DB or with any transactional database, and therefore there are some new rules for applying the Java Collections API. In addition, the Java API data store, index and foreign key APIs are outside the scope of the Java Co
