Object-relational mapping products should be be used when you want to take advantage of transparent persistence and use a relational database. A relational database may be required because:
- The data already resides in one or more relational databases
- The data is new, but there are technical or political reasons for using a relational database
In either case, an object-relational mapping product will reduce your programming code and, through caching, improve performance over using an embedded SQL or call-level interface with a relational database manager. Also see:
- Transparent persistence
- Transparent persistence vs. JDBC call-level interface
- Development Costs with Object-Relational Mapping Products
- Caching for Object-Relational Mapping
For how to use object-relational mapping with Java application servers, see enterprise architectures using Java application servers.
Context for When Object-Relational Mapping Should Be Used
Related Articles for When Object-Relational Mapping Should Be Used
The Savvy Manager's Guide
Douglas K Barry is also the author of a book that explains Web Services, service-oriented architecture, and Cloud Computing in an easy-to-understand, non-technical manner.
Web Services, Service-Oriented Architectures, and Cloud Computing: The Savvy Manager's Guide (Second Edition)
by Douglas K Barry with David Dick
This is a guide for the savvy manager who wants to capitalize on the wave of change that is occurring with Web Services, service-oriented architecture, and—more recently—Cloud Computing. The changes wrought by these technologies will require both a basic grasp of the technologies and an effective way to deal with how these changes will affect the people who build and use the systems in our organizations. This book covers both issues. Managers at all levels of all organizations must be aware of both the changes that we are now seeing and ways to deal with issues created by those changes.