One Model to Reduce Development and Maintenance Costs
Because an ODBMS stores exactly the same object model that is used at the application level, both development and maintenance costs can be reduced. With an ODBMS, there is no need to:
- Develop two data models: an object model in the application and a relational model stored in the database. This is not needed because an ODBMS uses the same object model as the application.
- Maintain two data models. An ODBMS eliminates the maintenance cost of keeping the to data models synchronized.
- Develop mapping between the relational and the object models. This is not needed because an ODBMS uses the same object model as the application.
- Maintain the mapping between the relational and object models. An ODBMS eliminates the maintenance cost of maintaining the mapping whenever there is a change to the object or relational model.
The result is that for a development team of six to seven, it is possible to have a team with one less person when using an ODBMS. It is typical when developing an object application with a RDBMS that one person is in charge of keeping the relational model synchronized with an object model and the mapping code. That person would not be needed in an ODBMS development project.
More on the general topic: When an Object Database Should Be Used