Object Oriented Database Learning Center

Objectivity Home - Government - Objectivity/DB - Webinars - Download Software

Download a PDF version of this Article

Table of contents:

Object Oriented Database vs Relational Database

• Introduction
• The Wall: Where an RDBMS breaks down
• Programming Time and Cost
• Integrity Loss
• Performance
• Information Model Issues
• Architecture Issues
• Benchmark
• Benchmark Parameters
• Benchmark Execution
• Parts Creation
• Updates
• Deletes
• Selects
• Summary
• Examples
• Cimskil (Manufacturing)
• Exxon (Configuration and FEA)
• CERN (Data Gathering and Analysis)
• Decision•ism (Decision Supportware)
• QUALCOMM (Telecommunications)
• COM21 (Cable Modem)
• Nortel, Sprint (Cell Phone Base Station Management)
• Nousoft (Library Document Management, Web)
• Iridium (Telecommunications)
• BBN (Military Logistics and Control)
• Intraspect (Knowledge Management)
• Fisher-Rosemount (Manufacturing, Process Control)
• A Brief Overview of Our Development
• ODB Selection
• Introduction
• Performance
• Scalability
• Productivity
• Fault Tolerance
• Additional Features and Benefits
• Summary
• Kintetsu (Transportation, Logistics)
• Siemens (Process Control)
• SEH (Semiconductor Manufacturing)
• NEC (Semiconductor Manufacturing)
• American Meter (Process Control)
• Sloan Digital Sky Survey (Geographic Information System)
• LMS (Healthcare, Fetal Monitoring)
• Synthesis (Healthcare, Record Management)
• Daikin (Multi-Media CD-I Authoring)
• How to Avoid the Wall

Object Oriented Database vs Relational Database

Scalability

Control Server Bottleneck

Most RDBMS are based on technology using a single server with multiple clients. Some OODBMS follow this pattern, but many are based on peer to peer technology. A peer to peer database system does not have the same potential performance bottleneck that a single server system poses. A peer to peer database system makes extensive use of the compute power and storage capacity on the client's computer.

Scalability by Adding Servers

In a peer to peer system performance problems are often solved by adding more compute power in the form of additional computers. In a client/server system adding more compute nodes makes the bottleneck problem at the server worse; the only option is to increase the server's horsepower.

Peer to peer systems scale better than client server systems. A peer to peer database system may easily and incrementally grow to handle the demands of an expanding application.

A fully distributed OODBMS has the capability to use disk storage any where in the network. This allows much flexibility in adding incremental storage capacity. An additional performance benefit may also be realized by placing persistent objects on the computer's disk where that information is most likely to be used.