Compatibility
Projects require increasing flexibility across languages and platforms. An OODB should not hinder this flexibility in any way. However, platform support is costly because it requires significant testing and documentation. Consequently, some vendors support their product on only a small number of platforms. Finding a solution that tightly integrates with the major OO languages, C++, Java, and Smalltalk, is quite difficult.
| Criteria |
Look for... |
| Supported platforms |
Broad platform support—I always look for the "key three": Linux, Win2000, and Solaris. Your priorities may vary. |
| Java integration |
Broad JDK support that closely tracks the current JDK specification |
| C++ integration |
Broad compiler support |
| Specialization of persistent classes |
Avoid tight coupling—look for databases that do not require modification of all persistent classes in the code. This is a preference, so you should research the pros and cons of post-processed enhancers versus extends/implements approaches. |
| Embeddable version |
Small footprints in disk; RAM; the ability to opt out of some non-core features |
Introduction
Introduction 
Performance and Scalability/Availability 
Product Reviews 
The