Why choose an object oriented database such as Objectivity/DB? Here’s a simplification:

In your everyday database (“relational database”) the data is stored in something like columns and rows. That’s an efficient, straightforward system for some applications, like the checkbook in your pocket or the spreadsheet on your desktop. The problem is, the best cutting-edge applications often use object programming languages like Java, C#, Visual Basic .NET, C++ and Smalltalk, which use data differently: these languages treat data as objects instead of columns and rows. Checkbook technology is out of its depth.

An object oriented database, on the other hand, stores data in the same format that these brilliant, flexible languages use – in other words, it stores data as objects -- so there’s no need to translate data back and forth as your application does its thing.

And that means power, accuracy and speed, glorious speed. The general rule: if you have a business need for it, and you have complex data, and you need things done quickly (and by that we mean that you need a product developed quickly, or that it needs to work fast, or both), an object oriented database is the only way to go.

Cutting-edge companies with the most demanding data needs have already adopted object oriented databases. Objectivity/DB has proven its value in business sectors such as:

• Government Military Command & Control
• Government Security & Intelligence
• Manufacturing, Process Control & Automation
• Life Sciences & Medical Equipment
• Data-Intensive Sciences
• Financial Services
• Internet Infrastructure

Object oriented databases:

• can handle high-performance processing and complex data
• in some cases, can accommodate unlimited application scalability
• can exhibit real-time performance
• have very high ingest rates
• are highly flexible
• perform with mission-critical reliability
• can help accelerate time to market
• work well with object-oriented programming languages such as Java, C#, Visual Basic .NET, C++ and Smalltalk