Databases: Difference between revisions
(reworking content, adding links, clarifying info) |
(→Subject-predicate-object database: + another important list to consider and other tweaks) |
||
| Line 21: | Line 21: | ||
== Subject-predicate-object database == | == Subject-predicate-object database == | ||
Subject-predicate-object databases basically construct [[w:semantic]] networks from interlinked atomic units called a [[w:triplet]]. | Subject-predicate-object databases basically construct [[w:semantic]] networks from interlinked atomic units called a [[w:triplet]] so they are not fundamentally different from graph databases in functionality and utility offered. | ||
These networks may be queried with a suitable query language such as [[w:SPARQL]] which in practice allows you to compose semantic queries. | These networks may be queried with a suitable query language such as [[w:SPARQL]] which in practice allows you to compose semantic queries. | ||
| Line 34: | Line 34: | ||
A [[w:triplestore]] maybe a native implementation from ground up or be standing on the shoulders of a standard RDBMS system where actual [[w:SQL]] is formulated by the interpreter and then queried from SQL. This probably has upsides and downsides. | A [[w:triplestore]] maybe a native implementation from ground up or be standing on the shoulders of a standard RDBMS system where actual [[w:SQL]] is formulated by the interpreter and then queried from SQL. This probably has upsides and downsides. | ||
=== Lists and comparisons of subject-predicate-object databases === | === Lists and comparisons of subject-predicate-object databases and SPARQL implementations === | ||
* [[w:List of subject-predicate-object databases|Wikipedia's list of subject-predicate-object databases]] | * [[w:List of subject-predicate-object databases|Wikipedia's list of subject-predicate-object databases]] | ||
* [[w:List of SPARQL implementations|Wikipedia's list of SPARQL implementations]] | |||
== Graph database == | == Graph database == | ||
Revision as of 14:43, 26 August 2016
This article is about choice of database models and implementations.
Known types of databases
- w:Relational database provided by a w:RDBMS
- Subject-predicate-object database are provided by w:Triplestores , native or on top of RDBMS
- w:Graph databases would intuitively appear more advanced than using RDF-triplet composed semantic networks.
- w:Object databases were a supposed fad in the late 80's and early 90's as w:relational algebra based systems are quite old.
Relational database
Together Consumerium and Consumium run all the 3 major free full fledged RDBMS there are: w:MariaDB, w:MySQL and w:Postgresql.
Relevant relational database powered software
- MediaWikis run on w:MySQL or the better and more ethical binary compatible drop-in replacement w:MariaDB. A recent fork by the original MySQL founders from MySQL.
The Netherlands server serving the Consumium free social media run on MariaDB 10
- https://d.consumium.org since 2013 and the rest mentioned on the landing page over there since 2016
- Postgresql is also in use working as data storage for w:GNU MediaGoblin at https://media.consumium.org
Subject-predicate-object database
Subject-predicate-object databases basically construct w:semantic networks from interlinked atomic units called a w:triplet so they are not fundamentally different from graph databases in functionality and utility offered.
These networks may be queried with a suitable query language such as w:SPARQL which in practice allows you to compose semantic queries.
Relevant subject-predicate-object database powered systems to interoperate with
Things to consider in selection of triplestore
A w:triplestore maybe a native implementation from ground up or be standing on the shoulders of a standard RDBMS system where actual w:SQL is formulated by the interpreter and then queried from SQL. This probably has upsides and downsides.