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

BBN
(Military Logistics and Control)

BBN, the creators of the Internet, have deployed a Crisis Management and Resource Logistics Management system built on Objectivity/DB. It supports distributed usage through multiple nodes in the field, for military and civilian crises that require immediate sharing of knowledge and optimization of resource allocation. For example, it was used after the Kobe, Japan, earthquake to coordinate rescue operations.

The top three requirements that led to the choice of the ODBMS are scalability, flexibility, and survivability. The first is due to the need to support massive operations, without the worry that a central server will overload. Instead, they can simple add more servers as needed.

Flexibility is required to support field deployment with constantly changing distribution models, nodes being attached and removed, while communication stays the same and integrity is ensured. In addition to such physical flexibility, it also requires the logical flexibility to support changing and adding object types online.

Finally, survivability is a necessity in such life-threatening operations. No single failure can disable the system, due to replication and use of multiple parallel servers. Also, there is never a need to disable the system due to the 24x7 operation capability.