There are many companies producing object databases for Java.
In future months we will interview one of them and ask about the
tools and environments they will be creating for development and
deployment of applications. The following list of object data
management requirements has been taken from Object data management
by R.G.G. Cattell.
- Unique Object Identifiers each object must have a
unique ID to be identified. These IDs must potentially exist for
a long time, Don't assume 232 is enough.
- Composite Objects it is important to store an object that
consists of many different object types.
- References and Integrity the referential integrity
of objects must be improved over traditional DBMS applications.
- Object-type hierarchy support in the database for inheritance
of an object type.
- Associated procedures storing of procedures as well
as data.
- Object encapsulation support n the DBMS for encapsulation.
- Ordered sets and references ordering of relationships
for an object and support for lists of attributes rather than sets.
- Large Data Blocks efficient storage of audio, video,
and large class files.
- Efficient remote database access functionality in large
network environments.
- Ease of Schema changes ability to move to a new schema
easily.
- Programming language interface unified common interface
- Multiple database versions ability to have versions
of objects.
- Long term lock and checkout
- Performance saving objects over the network must be
transparent and competitive with traditional storage techniques.
- Ability to support distributed database object stores.