When an Object Database Should Be Used
Consider an object database when you have a business need for high performance on complex data. Generally, an object database is a good choice when you have all three factors: business need, high performance, and complex data.
Recently, people have also been considering an object database even when their data is not particularly complex. An object database can allow for a smaller team and faster development because there is only one data model. More information on these topics can be found in the related content below.
More Detail on When an Object Database Should Be Used
Context for When an Object Database Should Be Used
Related Articles for When an Object Database Should Be Used
- Object-Oriented Database Management System (OODBMS) Definition
- ODBMS FAQ
- Caching for Object Database Management Systems
- Architectures That Use Object Database Products
- Everyday Uses of Object Databases
- ODBMS Myths
- Object Database Problems?
Author
Douglas K Barry
Principal
Barry & Associates, Inc.
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.