Content deleted Content added
m Spelling correction; redirect bypass from W3c to World Wide Web Consortium using popups |
Rescuing 1 sources and tagging 0 as dead.) #IABot (v2.0.9.5 |
||
| (37 intermediate revisions by 30 users not shown) | |||
Line 1:
{{
[[File:Object-Oriented Model.svg|thumb|320px|Example of an object-oriented model<ref name="USDT01">[http://knowledge.fhwa.dot.gov/tam/aashto.nsf/All+Documents/4825476B2B5C687285256B1F00544258/$FILE/DIGloss.pdf Data Integration Glossary] {{webarchive |url=https://web.archive.org/web/20090320001015/http://knowledge.fhwa.dot.gov/tam/aashto.nsf/All+Documents/4825476B2B5C687285256B1F00544258/$FILE/DIGloss.pdf |date=March 20, 2009 }}, U.S. Department of Transportation, August 2001.</ref>]]
An '''object database''' or '''object-oriented database''' is a [[database management system]] in which information is represented in the form of [[Object (computer science)|objects]] as used in [[object-oriented programming]]. Object databases are different from [[relational database]]s which are table-oriented. A third type, [[
Object databases have been considered since the early 1980s.<ref>[http://odbms.org/Introduction/history.aspx ODBMS.ORG :: Object Database (ODBMS) | Object-Oriented Database (OODBMS) | Free Resource Portal]. ODBMS (2013-08-31). Retrieved on 2013-09-18. {{webarchive |url=https://web.archive.org/web/
▲Object databases have been considered since the early 1980s.<ref>[http://odbms.org/Introduction/history.aspx ODBMS.ORG :: Object Database (ODBMS) | Object-Oriented Database (OODBMS) | Free Resource Portal]. ODBMS (2013-08-31). Retrieved on 2013-09-18. {{webarchive |url=https://web.archive.org/web/20140725090329/http://odbms.org/Introduction/history.aspx |date=July 25, 2014 }}</ref>
==Overview==
Object-oriented database management systems (OODBMSs) also called ODBMS (Object Database Management System) combine database capabilities with [[object-oriented programming]] language capabilities.
OODBMSs allow object-oriented programmers to develop the product, store them as objects, and replicate or modify existing objects to make new objects within the OODBMS. Because the database is integrated with the programming language, the programmer can maintain consistency within one environment, in that both the OODBMS and the programming language will use the same model of representation. Relational DBMS projects, by way of contrast, maintain a clearer division between the [[database model]] and the application.
As the usage of web-based technology increases with the implementation of Intranets and extranets, companies have a vested interest in OODBMSs to display their complex data. Using a DBMS that has been specifically designed to store data as objects gives an advantage to those companies that are geared towards multimedia presentation or organizations that utilize [[computer-aided design]] (CAD).<ref>O’Brien, J. A., & Marakas, G. M. (2009). Management Information Systems (9th ed.). New York, NY: McGraw-Hill/Irwin</ref>
Some object-oriented databases are designed to work well with [[object-oriented programming language]]s such as [[
==History==
Object database management systems grew out of research during the early to mid-1970s into having intrinsic database management support for graph-structured objects. The term "object-oriented database system" first appeared around 1985.<ref>Three example references from 1985 that use the term: T. Atwood, "An Object-Oriented DBMS for Design Support Applications
Early commercial products included [[GemStone Systems|Gemstone]] (Servio Logic, name changed to GemStone Systems), Gbase (Graphael), and Vbase (Ontologic). Additional commercial products entered the market in the late 1980s through the mid 1990s. These included ITASCA (Itasca Systems), Jasmine (Fujitsu, marketed by Computer Associates), Matisse (Matisse Software), [[Objectivity/DB]] (Objectivity, Inc.), [[ObjectStore]] ([[Progress Software]], acquired from eXcelon which was originally [[Object Design, Incorporated]]), ONTOS (Ontos, Inc., name changed from Ontologic), O<sub>2</sub><ref>Bancilhon, Francois; Delobel, Claude; and Kanellakis, Paris. ''Building an Object-Oriented Database System: The Story of O<sub>2</sub>.'' Morgan Kaufmann Publishers, 1992. {{ISBN|1-55860-169-4}}.</ref> (O<sub>2</sub> Technology, merged with several companies, acquired by [[Informix]], which was in turn acquired by [[IBM]]), POET (now [http://www.versant.com/developer FastObjects] from Versant which acquired Poet Software), Versant Object Database ([http://www.versant.com Versant] Corporation), VOSS (Logic Arts) and [[JADE (programming language)|JADE]] (Jade Software Corporation). Some of these products remain on the market and have been joined by new open source and commercial products such as [[InterSystems Caché]].
Object database management systems added the concept of [[persistence (computer science)|persistence]] to object programming languages. The early commercial products were integrated with various languages: GemStone ([[Smalltalk]]), Gbase ([[LISP programming language|LISP]]), Vbase ([[C Object Processor|COP]]) and VOSS (Virtual Object Storage System for [[Smalltalk]]). For much of the 1990s, [[C++]] dominated the commercial object database management market. Vendors added [[Java programming language|Java]] in the late 1990s and more recently, [[C Sharp (programming language)|C#]].
Starting in 2004, object databases have seen a second growth period when [[Open-source software|open source]] object databases emerged that were widely affordable and easy to use, because they are entirely written in [[Object-oriented programming|OOP]] languages like Smalltalk, Java, or C#, such as Versant's [[db4o]] (db4objects), DTS/S1 from Obsidian Dynamics and [[Perst]] (McObject), available under dual [[Open-source license|open source]] and commercial licensing.
==Timeline==
Line 29 ⟶ 28:
** [[InterSystems]] M
* 1980
** TORNADO – an object database for [[CAD/CAM]]<ref>{{cite journal|last1=Ulfsby|title=TORNADO: a DBMS for CAD/CAM systems|journal=[[Computer-Aided Design
* 1982
** [[Gemstone (database)|Gemstone]] started (as Servio Logic) to build a set theoretic model data base machine.
Line 62 ⟶ 61:
* 2004 db4o's commercial launch as db4objects, Inc.
* 2008 db4o acquired by [[Versant Corporation]]
* 2010 [[VMware]] acquires GemStone<ref>{{Cite web|url=http://www.vmware.com/company/news/releases/spring-gemstone.html|title=SpringSource to Acquire Gemstone Systems Data Management Technology|date=May 6, 2010|
* 2011 db4o's development stopped.
* 2012
* 2013 GemTalk Systems acquires [[Gemstone (database)|Gemstone]] products from VMware<ref name=gemtalk1>{{Cite web|url=http://www.prweb.com/releases/gemtalksystems/acquires-gemstone-s/prweb10652596.htm|author=GemTalk Systems|publisher=PRWeb|date=May 2, 2013|title=GemTalk Systems Acquires GemStone/S Products from VMware|accessdate=August 5, 2014|url-status=live|archiveurl=https://web.archive.org/web/20140810224807/http://www.prweb.com/releases/gemtalksystems/acquires-gemstone-s/prweb10652596.htm|archivedate=August 10, 2014}}</ref>▼
* 2012 [[Actian]] acquires Versant Corporation
* 2014 [[Realm (database)|Realm]] <ref>{{cite web|url=https://www.infoq.com/news/2016/11/Realm-database-nodejs|title=Realm Releases Object Database for Node.js|website=InfoQ|url-status=live|archiveurl=https://web.archive.org/web/20170202043544/https://www.infoq.com/news/2016/11/Realm-database-nodejs|archivedate=2017-02-02}}</ref>▼
▲* 2013 GemTalk Systems acquires [[Gemstone (database)|Gemstone]] products from VMware<ref name=gemtalk1>{{Cite web|url=http://www.prweb.com/releases/gemtalksystems/acquires-gemstone-s/prweb10652596.htm|author=GemTalk Systems|publisher=PRWeb|date=May 2, 2013|title=GemTalk Systems Acquires GemStone/S Products from VMware|
* 2014 db4o's commercial offering is officially discontinued by Actian (which had acquired Versant)<ref>{{cite web|url=http://supportservices-old.actian.com/versant/default.html|title=restructuring our Versant Community Website}}</ref>
▲* 2014 [[Realm (database)|Realm]]
*2017 ObjectBox<ref>{{Cite web|last=DB-Engines|title=Object Database Ranking on DB-Engines|url=https://db-engines.com/en/ranking/object+oriented+dbms|access-date=2021-05-21|website=DB-Engines}}</ref>
==Adoption of object databases==
Object databases based on persistent programming acquired a niche in application areas such as
engineering and [[Object-based spatial database|spatial databases]], [[telecommunications]], and scientific areas such as [[Particle physics|high energy physics]]<ref>{{Cite web|url=https://www.service-architecture.com/articles/object-oriented-databases/stanford-linear-accelerator.html|title = Stanford Linear Accelerator (SLAC)}}</ref> and [[molecular biology]].<ref>{{
Another group of object databases focuses on embedded use in devices, packaged software, and [[Real-time computing|real-time]] systems.
Line 87 ⟶ 90:
==Standards==
The [[Object Data Management Group]] was a consortium of object database and
Many object database ideas were also absorbed into [[SQL:1999]] and have been implemented in varying degrees in [[
In 2005 Cook, Rai, and Rosenberger proposed to drop all standardization efforts to introduce additional object-oriented query APIs but rather use the OO programming language itself, i.e., Java and .NET, to express queries. As a result, [[Native Queries]] emerged. Similarly, Microsoft announced [[Language Integrated Query]] (LINQ) and DLINQ, an implementation of LINQ, in September 2005, to provide close, language-integrated database query capabilities with its programming languages C# and VB.NET 9.
Line 95 ⟶ 98:
In February 2006, the [[Object Management Group]] (OMG) announced that they had been granted the right to develop new specifications based on the ODMG 3.0 specification and the formation of the Object Database Technology Working Group (ODBT WG). The ODBT WG planned to create a set of standards that would incorporate advances in object database technology (e.g., replication), data management (e.g., spatial indexing), and data formats (e.g., XML) and to include new features into these standards that support domains where object databases are being adopted (e.g., real-time systems). The work of the ODBT WG was suspended in March 2009 when, subsequent to the economic turmoil in late 2008, the ODB vendors involved in this effort decided to focus their resources elsewhere.
In January 2007 the [[World Wide Web Consortium]] gave final recommendation status to the [[XQuery]] language. XQuery uses [[
[[XQuery|XQuery v1]] and [[XPath 2.0|XPath v2]] and later are powerful and are available in both open source and libre (FOSS) software,<ref>{{cite web|url=https://basex.org/basex/xquery/|title=BaseX XQuery Processor|website=basex.org|url-status=live|archive-url=https://web.archive.org/web/20231216035330/https://basex.org/basex/xquery/|archive-date=2023-12-16}}</ref><ref>{{cite web|url=https://exist-db.org/exist/apps/doc/xquery|title=XQuery in eXist-db|website=exist-db.org|url-status=live|archive-url=https://web.archive.org/web/20231202052435/https://exist-db.org/exist/apps/doc/xquery|archive-date=2023-12-02}}</ref><ref>{{cite web|url=https://www.saxonica.com/html/documentation/using-xquery/index.html|title=Saxon - Using XQuery|website=www.saxonica.com|url-status=live|archive-url=https://web.archive.org/web/20200923004515/https://www.saxonica.com/html/documentation/using-xquery/index.html|archive-date=2020-09-23}}</ref> as well as in commercial systems. They are easy to learn and use, and very powerful and fast. They are not relational and XQuery is not based on SQL (although one of the people who designed XQuery also co-invented SQL). But they are also not object-oriented, in the programming sense: XQuery does not use encapsulation with hiding, implicit dispatch, and classes and methods. XQuery databases generally use XML and JSON as an interchange format, although other formats are used.
In January 2016, with the [[PostgreSQL|PostgreSQL 9.5 release]]<ref>{{cite web|url=https://www.postgresql.org/docs/current/static/functions-json.html|title=PostgreSQL: Documentation: 10: 9.15. JSON Functions and Operators|website=www.postgresql.org|url-status=live|
==Comparison with RDBMSs==
An object database stores complex data and relationships between data directly, without mapping to relational [[Row (database)|rows]] and [[Column (database)|columns]], and this makes them suitable for applications dealing with very complex data.<ref>{{Cite journal | last=Radding | first=Alan | year=1995 | title=So what the Hell is ODBMS? | journal=Computerworld | volume=29 | issue=45 | pages=121–122, 129}}</ref> Objects have a many-to-many relationship and are accessed by the use of pointers. Pointers are linked to objects to establish relationships. Another benefit of an OODBMS is that it can be programmed with small procedural differences without affecting the entire system.<ref>Burleson, Donald. (1994). OODBMSs gaining MIS ground but RDBMSs still own the road. Software Magazine, 14(11), 63</ref>
==See also==
Line 111 ⟶ 116:
* [[NoSQL]]
* [[Object Data Management Group]]
* [[
* [[Persistence (computer science)]]
* [[Relational model]]
Line 121 ⟶ 126:
==External links==
* [http://www.odbms.org/ Object DBMS resource portal]
* [http://db-engines.com/en/ranking/object+oriented+dbms Ranking of Object Oriented DBMS] {{Webarchive|url=https://web.archive.org/web/20241201172721/https://db-engines.com/en/ranking/object%2Boriented%2Bdbms |date=2024-12-01 }} - by popularity, updated monthly from [[DB-Engines ranking|DB-Engines]]
{{Database models}}
{{Authority control}}
{{DEFAULTSORT:Object Database}}
| |||