Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.
- Database file size up to 128 TB (= 131,072 GB = 134,217,728 MB).
- Up to 2,147,483,648 entity classes per database file.
- Up to 2,147,483,648 indexes per database file.
- Up to 9,223,372,036,854,775,808 entity objects per database file.
- Unlimited database connections (limited by operating system resources).
ObjectDB requires Java 5 or later (Java 6 is preferred). As a pure Java application, ObjectDB should be able to run on any platform that supports the Java Standard Edition. Either the Java Development Kit (JDK) or the Java Runtime Environment (JRE) can be used. A version of ObjectDB for .NET is currently under development.
ObjectDB can be used by Java Virtual Machine (JVM) languages, such as Java, Groovy and Scala. It can also be used with other languages, such as Phyton, Ruby and PHP, but currently only with their JVM implementations (e.g. Jython for Phyton, JRuby for Ruby and Quercus for PHP). A version of ObjectDB for .NET is currently under development and future support for other languages (including full Phyton, PHP and Ruby support) is planned.
To access relational databases using the Java Persistence API (JPA) you will need an Object Relational Mapping (ORM) tool, such as Hibernate, TopLink, EclipseLink, Open JPA or DataNucleus. The DataNucleus ORM implementation supports also the Java Data Objects (JDO) API. ObjectDB is a full featured standalone Object Database Management System (ODBMS) and not an ORM tool, so it is not intended and cannot be used to access other database management systems.
ObjectDB is highly scalable and can manage efficiently databases in a wide range of sizes, from a few Kilobytes to hundreds of Gigabytes and even Terabytes. ObjectDB can be used in small embedded single user applications as well as in heavy loaded multi threaded multi user applications.