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:

Building High-perfomance Object Oriented Databases

• The Problem
• High ingest rates
• High delete/archival rates
• Complex relationships
• Flexibility
• Performance Optimization
• Very Large Cardinalities
• A Solution
• Persistence
• The Hierarchical Solution
• The Relational Solution
• An Object-oriented approach to persistence
• Query/Retrieval
• Query by Attribute
• Query by Traversal
• Cache
• Concurrency
• Schema Control and Data Migration
• Transactions (Commit / Rollback)
• Single, Consistent View of Data
• A Practical Example
• Logical Schema
• Message Class
• Attachments and Relationships
• Sender, Recipients, CC Lists and Addresses
• Physical Data Placement
• Using Databases and Containers for Fast Archival and Deletes
• Using Databases and Containers for Fast Queries
• Using Databases, Containers and Range Lists for Parallel Queries
• Hardware Architecture Design and Sizing
• Objectivity/DB Terminology

High delete/archival rates: Applications that are constantly streaming in new data often have a need to archive older data and keep newer data online.

For most SQL databases this requires a query on all tables by time and a complex mechanism to copy the data (atomically) to another storage repository and then delete it from the database.

The overhead in terms of processing and I/O involved in this operation is very large. Reversing the process and restoring archived data into the original repository can be equally difficult.

Again, this is a direct result of organizing data into tables. It may make much more sense to reorganize the data from several tables by time, rather than by type, especially if most of the user queries to fetch the data will have a time constraint as well.