JPA has standardized the interfaces for persistence frameworks. However how much is standardized regarding the runtime behaviour of frameworks. These small code samples show different uses cases to test with your JPA framworks. Additionally hints on the actual framework behaviour, will help to improve usage.

Sorta like a couch except smaller and outside, also, a client side JSON document store. Perfect for webkit mobile apps that need a lightweight, simple and elegant persistence solution.

db4o Maven snapshot repository is now available. Responding to a frequent request from the community, the db4o team now supplies Maven snapshots of both the stable and the trunk (continous) db4o builds. The repository is available at the following URL: https://source.db4o.com/maven The artifact layout corresponds to the structure you find in the regular downloads. It has changed between versions 7.4 and 7.12: In 7.12 they factored out the optional and cs (Client/Server) modules to become separate jars and supply a full (no dependency) jar that contains the full db4o distribution including all required and optional modules.

db4o Deep Prefetching for C/S mode is examined via runtime statistics (a facility that allow you to track db4o behavior). (Even if you don't use db4o in C/S mode, it may still be worthwhile to keep on reading, since some of the observations made apply to db4o configuration optimization in general - or actually even more, to performance tweaking in general)

The idea behind Taban is that an web application will simply use HTTP methods (GET, PUT and DELETE) to perform the usual CRUD operations required for persistence, but using JSON as the data exchange format. Taban is (will be) implemented as OSGi bundles and will call out to/depend on a number of OSGi services. db4o is to provide the default implementation of the database.