Content deleted Content added
+ C# |
m Updating for latest features and removing outdated ones. |
||
Line 3:
| advert=January 2010
}}
'''Objectivity/DB''' is a commercial [[object database]] produced by Objectivity, Inc. It allows applications to make standard [[C++]], [[C Sharp (programming language)|C#]], [[Java (programming language)|Java]], or [[Python (programming language)|Python
== History ==
Objectivity, Inc. was founded in 1988 and brought Objectivity/DB to the market in 1990. The corporate headquarters is in [[San Jose, California|San Jose]], [[California]]. The company was a founding member of both the [[Object Management Group]] (OMG) and the [[Object Data Management Group]] (ODMG). The C++
== Architectural features ==
Objectivity/DB is a [[distributed database]] that provides a single logical view across a federation of databases distributed across the network. It uses a [[distributed computing]] model that links a small software library with the client application. The client transparently communicates with remote servers that are functionally simpler than their equivalents in [[centralized database]] server architectures. There are lock, remote data transfer and query agent server processes. The distributed architecture helps make Objectivity/DB inherently [[scalability|scalable]] and [[reliability (engineering)|reliable]]. It has sustained ingest rates in excess of one terabyte per hour while simultaneously supporting data fusion and query operations.<ref>[http://www.objectivity.com/pages/object-oriented-databases/building_high_performance_object_oriented_databases.html Building a High Throughput Data repository With High Query Performance] 2004</ref>
Objectivity/DB uses a
Objectivity/DB provides a flexible approach for defining how objects are placed within a given storage hierarchy. Database designers can define a custom placement strategy that is encapsulated in an XML configuration file and made available to the application. This strategy can define which persistent objects are stored together, which are distributed, and which are stored near designated objects.
Objects can be linked to other objects using named uni-directional or bi-directional links. The links can have a [[cardinality]] of 1:1, 1:many, many:1 or many:many and use the OIDs to speed up the navigation of networks of objects. The OIDs are also used in support of scalable collections (tree, list, set etc.), indices and [[hash table]]s. Eliminating the relational [[Join]] operations inherent in a relational database gives Objectivity/DB a marked performance advantage.▼
▲Objects can be linked to other objects using named uni-directional or bi-directional links. The links can have a [[cardinality]] of 1:1, 1:many, many:1 or many:many and use the OIDs to speed up the navigation of networks of objects. The OIDs are also used in support of scalable collections (tree, list, set etc.), indices and [[hash table]]s. Eliminating the relational [[Join]] operations inherent in a relational database gives Objectivity/DB a marked performance advantage, in orders of magnitude.
Objectivity/DB is also different from [[RDBMS]]s in the way in which it handles queries. The application declares and initializes an iterator that locates and returns qualified objects as soon as they are located. Many RDBMSs manifest a view of the results before returning any of them. The Objectivity/DB Parallel Query Engine splits queries into subtasks directed at individual databases or containers. Remote query agents service each subtask and return results to the iterator. The Parallel Query Engine has two replaceable components: a splitter that can determine how to best subdivide the task and a filter in the query agent that can further refine a query. A query involving cities in Europe might be split into forty nine subtasks, one for each country. The filter might access an external data source before qualifying or disqualifying the objects that the Query Agent has found in the Objectivity/DB database or container.<ref>[http://www.odbms.org/download/025.01%20Guzenda%20The%20Evolution%20of%20a%20Distributed,%20Federated%20Object%20Query%20Engine%20June%202006.PDF The evolution of a distributed, federated object query engine] Leon Guzenda, June 2006</ref>
Line 21 ⟶ 23:
Databases and system data (catalogs and [[Database schema|schema]]) can be replicated to multiple locations using a quorum based synchronous replication mechanism. Replicas that are temporarily separated from the quorum are transparently resynchronized when they are reconnected to the network that services them and their peers. Individual databases and lock servers can be allocated votes that are used to determine whether or not a client can update a replica.
The distributed database and processing architecture of Objectivity/DB has allowed it to be used in many [[grid computing]] environments. It has attained certification as an IBM Ready For Grid product. It is also used in [[Service Oriented Architecture]] applications. Objectivity For Java has support for the [[J2EE Connector Architecture]] (JCA) standard. The distributed architecture of Objectivity/DB is equally applicable to cloud environments.
== Typical applications ==
Line 27 ⟶ 29:
Objectivity/DB is generally used in data intensive or real-time applications that manipulate highly complex, inter-related data. It may be embedded in a software or hardware product or used as a part of commercial, scientific or government project.
Early deployments were primarily in [[Computer-Aided Design]] and engineering applications. In the early 1990s a number of telecom equipment manufacturers started embedding Objectivity/DB in advanced [[intelligent network]] and [[element management systems]]. Notable deployments
Defense contractors and large science projects started using Objectivity/DB in the late 1990s. The government applications cover command and control, security, data fusion and intelligence applications. Objectivity/DB has been used in astrophysics, high energy physics, fusion, earth sciences, hydrography and bioinformatics applications. Most of these applications build and manipulate extremely large (
The choice of an RDBMS or an ODBMS depends on many factors. An ODBMS can be ideal in a compute or data intensive object oriented system. However, if an RDBMS can comfortably meet the functional and performance requirements of an application with the available programming resources then there is probably no need to consider an ODBMS.
| |||