Object Oriented Database Learning Center

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

Download a PDF version of this Article

Learning Center Home

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

A Brief Overview of Our Development:

Objectivity is being used at FRSI in several areas:

• As the database for an existing Console product
• As the database for our Batch Historian
• As the integrated database for a future product line

In these 3 areas Objectivity is being used to store configuration data and to store production data. In the first release of the future product we anticipate a very complex configuration with over 500 classes with a "web" of over a 1000 associations. The configuration database will store approx. 100 MBytes of configuration. The production database will store several GBytes of data.

The selection criteria for us included:

• Reliability: the database must be able to operate in a 7x24 situation for many months at a time.
• Concurrency: the database must be able to be "pounded" on by several users and many processes at the same time. We have several transaction models in place for dealing with different levels of access.
• Performance: with such a complex schema, i.e., many different objects with v ery different compositions and many associations between classes, performance is a key consideration.