Leaving the Data in a Relational Database and Using an Object Database
With the advent of multi-tier architectures, it can be useful to leave the data in the relational database and also use an object database. The relational database can then serve as the database of record and continue to support existing applications. Data can also be converted and stored in the object database to serve the needs of high-performance Internet access. See the example of a middle tier architecture that uses object-relational mapping and an object database.
See the related content below. This is the last page for the example of using existing relational schema.
Context for Leaving the Data in a Relational Database and Using an Object Database
Related Articles for Leaving the Data in a Relational Database and Using an Object Database
Author
Douglas K Barry
Principal
You may use this material for your work or classes. Reprint Policy. Be sure to check the menu at the left for other articles available on this site.
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.