ct that uses a standard language will be more flexible and portable.
Scalability:
What is the largest database the product will support? What is the largest database using the product that is up and running? How many users access the database at one time?
Security:
How is security determined -- by user, group, or both?
Backup and recovery:
How does the product handle backup and recovery?
Transactions:
Does the database allow for transaction logging, recovery, and rollback?
Methods:
How does the ODBMS store methods? To be a true ODBMS, it should store them in the database itself.
Collection classes:
What collection classes can the database handle? The ODMG, Java, and several object class libraries -- notably STL -- have defined certain common collection classes. Use of standardized collection classes increases portability and flexibility.
Support and training:
What kind of support and training does the vendor offer? How long will it take to train your staff?
illustration_link (19 Kbytes)
Object databases are a good place to store business rules.
Selecting an ODBMS
