Objectivity/DB: Difference between revisions

Revision as of 22:19, 1 December 2014

Latest revision as of 14:26, 19 July 2025

(24 intermediate revisions by 21 users not shown)

Line 1:

{{Short description|Proprietary object database}}

{{Multiple issues|

| COI=July 2010

{{COI| advertdate=JanuaryJuly 2010}}

{{advert|date= January 2000 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]] objects persistent without having to convert the data objects into the rows and columns used by a [[relational database management system]] (RDBMS). Objectivity/DB supports the most popular object oriented languages plus [[SQL]]/[[ODBC]] and [[XML]]. It runs on [[Linux]], [[Macintosh]], [[UNIX]] and [[Microsoft Windows|Windows]] platforms. All of the languages and platforms interoperate, with the Objectivity/DB kernel taking care of compiler and hardware platform differences.

'''Objectivity/DB''' is a commercial [[object database]] produced by Objectivity, Inc. It allows applications to makestore standard [[C++]], [[C Sharp (programming language)|C#]], [[Java (programming language)|Java]], or [[Python (programming language)|Python]] objects persistentpersistently, without havingconverting to convert the data objectsthem into the rows and columns used by a [[relational database management system]] (RDBMS). Objectivity/DB supports the most popular object -oriented languages plusas well as [[SQL]]/[[ODBC]] and [[XML]]. It runsis oncompatible with [[Linux]], [[Macintosh]], [[UNIX]] and [[Microsoft Windows|Windows]] platforms. All of the languages and platforms interoperate, withfacilitating theinteroperability Objectivity/DBacross kerneldifferent taking care of compilerlanguages and hardware platformenvironments.{{citation differences.needed|date=May 2025}}

== History ==

== 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++ and Java interfaces for Objectivity/DB incorporate the features defined in the ODMG'93 standard.

Objectivity/DB was first introduced in 1990. The C++ and Java interfaces adhere to the ODMG'93 standard,<ref name="odmgBook">{{cite book|url=https://archive.org/details/isbn_9781558606470_0|title=Object Data Standard: ODMG 3.0|author1=R. G. Cattell|author2=Douglas K. Barry|author3=Mark Berler|author4=Mark Berler|author5=Jeff Eastman|author6=David Jordan|author7=Craig Russell|author8=Olaf Schadow|author9=Torsten Stanienda|author10=Fernando Velez|date=January 2000|publisher=Academic Press|isbn=1558606475|accessdate=December 1, 2014|url-access=registration}}</ref> with subsequent additions of C# and Python interfaces. Objectivity, Inc. ceased in late 2023.{{citation needed|date=May 2025}}

<ref name="odmgBook">

{{

cite web

|url= http://www.odbms.org/odmg-standard/odmg-book/

|title= Object Data Standard: ODMG 3.0

|author= R. G. Cattell (Editor), Douglas K. Barry (Editor), Mark Berler (Editor), Mark Berler, Jeff Eastman, David Jordan, Craig Russell, Olaf Schadow, Torsten Stanienda, Fernando Velez

|date= January 2000

|publisher= Academic Press

|isbn= 1-55860-647-5

|accessdate= December 1, 2014

}}

</ref> The C# and Python interfaces were added subsequently.

== 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 distributed storage hierarchy. Objects are stored in logical clusters called containers. The containers are stored in databases that are cataloged in a [[federated database]]. Every object has a unique 64-bit Object Identifier (OID) that is a composite logical structure. The physical address space limitation for a single federation is in the millions of Terabytes range. The largest publicized Objectivity/DB installation, at SLAC's [[BaBar experiment]], stored over a Petabyte of objects.<ref>[http://www.slac.stanford.edu/BFROOT/www/Public/Computing/Databases/proceedings/CIDR05.pdf Lessons Learned from Managing a Petabyte] Jacek Becla and Daniel L. Wang, 2005</ref><ref>[http://www.slac.stanford.edu/BFROOT/www/Public/Computing/Databases/ BaBar Database]</ref>

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, 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>

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.

== Architectural features ==

== Typical applications ==

Objectivity/DB operates as a [[distributed database]], providing a unified logical view across a network of databases. It employs a [[distributed computing]] model where client applications transparently communicate with simplified servers processes. This architecture enhances [[scalability]]<ref name="georgeTown">{{cite web|url=http://www.gsnmagazine.com/node/29210?c=cyber_security|title=Georgetown University taps Objectivity for Big Data research|date=May 2013|publisher=Government Security News|accessdate=December 1, 2014|archive-date=July 1, 2017|archive-url=https://web.archive.org/web/20170701004035/http://gsnmagazine.com/node/29210?c=cyber_security|url-status=dead}}</ref> and [[reliability (engineering)|reliability]], supporting ingest rates exceeding one terabyte per hour while concurrently facilitating data fusion and query operations.<ref name="panasasPaper">{{cite web|url=http://www.panasas.com/sites/default/files/uploads/docs/panasas_objectivity_wp_lr_1065.pdf|title=Scaling Objectivity Database Performance with Panasas® Scale-Out NAS Storage|date=August 2011|accessdate=December 1, 2014}}</ref>

Objectivity/DB usesutilizes a distributed storage hierarchy., Objectsstoring are storedobjects in logical clusters called containers. The containers are stored in databases that are cataloged in awithin [[federated database|federated databases]]. EveryEach object hasis assigned a unique 64-bit Object Identifier (OID) that iswithin a composite logical structure. Themassive physical address space limitation for a single federation is in thespanning millions of Terabytes range. TheNotably, the largest publicizedreported Objectivity/DB installation,deployment at SLAC's [[BaBar experiment]], stored over a Petabytepetabyte of objects.<ref>[http://www.slac.stanford.edu/BFROOT/www/Public/Computing/Databases/proceedings/CIDR05.pdf Lessons Learned from Managing a Petabyte] Jacek Becla and Daniel L. Wang, 2005</ref><ref>[http://www.slac.stanford.edu/BFROOT/www/Public/Computing/Databases/ BaBar Database]</ref>

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.

The database offers flexibility in defining object placement within its storage hierarchy.<ref name="placement">{{cite web|url=http://www.dataversity.net/objectivity-launches-objectivitydb-11-0/|title=Objectivity Launches Objectivity/DB 11.0|author=Angela Guess|date=February 6, 2013|publisher=DATAVERSITY|accessdate=December 2, 2014}}</ref> through customizable strategies encapsulated in XML configuration files. This approach allows database designers to specify how persistent objects are stored, distributed, and positioned relative to other designated objects.{{citation needed|date=May 2025}}

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 have included the wireless [[sprintpcs|SprintPCS]] and the [[Iridium satellite constellation|Iridium low Earth orbit satellite networks]]. A number of process control, manufacturing and medical instrumentation systems incorporate Objectivity/DB because of its real-time performance and high availability.

In Objectivity/DB, objects can establish named uni-directional or bi-directional links with other objects, supporting various [[Cardinality|cardinalities]] (1:1, 1, many:1, many). Object Identifiers (OIDs) expedite navigation across networks of objects,<ref name="bloor">{{cite web|url=http://www.bloorresearch.com/analysis/objectivity-infinitegraph/|title=Objectivity and InfiniteGraph|author=Philip Howard|date=May 29, 2012|publisher=Bloor|accessdate=December 1, 2014}}</ref> supporting scalable collections (tree, list, set etc.), indices, and [[hash table]]s. By eliminating relational [[Join (SQL)|Join]] operations typical in RDBMS, Objectivity/DB achieves enhanced performance advantages.<ref>{{cite book|author1=Suzanne W. Dietrich|author2=Susan D. Urban|year=2011|title=Fundamentals of Object Databases|publisher=Morgan & Claypool Publishers|page=2|isbn=9781608454761|url=https://books.google.com/books?id=x_8myOrO1dgC&q=Fundamentals+of+Object+Databases|accessdate=December 3, 2014}}</ref><ref>{{cite book|editor1=Alan Dearle|editor2=Roberto V. Zicari|year=2010|title=Objects and Databases, Third International Conference Proceedings, ICOODB|publisher=Springer|page=34|isbn=978-3642160912|url=https://books.google.com/books?id=AHHE015TBrIC|accessdate=December 3, 2014}}</ref><ref>{{cite book|author=C.S.R Prabhu|year=2011|title=Object-Oriented Database Systems - Approaches and Architecture, Third Edition|publisher=Asoke K. Ghosh, PHI Learning Private Limited|page=67|isbn=9788120340930|url=https://books.google.com/books?id=aRdl1j31MfoC|accessdate=December 3, 2014}}</ref>

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 (multi-Petabyte) databases.

The distributed architecture of Objectivity/DB has facilitated its adoption in [[grid computing]] environments and [[Service Oriented Architecture]] (SOA) applications. It holds certification as an IBM Ready for Grid product and supports the [[J2EE Connector Architecture]] (JCA) standard making it suitable for deployment in cloud environments.<ref name="cloudReady">{{cite web|url=http://www.neovise.com/node/89#|title=Objectivity: Complex Data-Management, Simplified|date=2014|publisher=Neovise|accessdate=December 2, 2014}}</ref>

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.

==References==

Line 51 ⟶ 25:

==External links==

* [http://www.objectivity.com/ Objectivity, Inc.]

* [http://www.odbms.org ODBMS.ORG]