Databases: Difference between revisions
expanding on the free w:RDBMS trio |
removed redundant paragraph with content already dealt with in the introduction to the free w:RDBMS trio |
||
| Line 15: | Line 15: | ||
* [[w:MySQL]], the most widely known of free databases powering this [[Development Wiki]] | * [[w:MySQL]], the most widely known of free databases powering this [[Development Wiki]] | ||
* [[w:PostgreSQL]] powering the https://media.consumium.org [[w:GNU MediaGoblin]] | * [[w:PostgreSQL]] powering the https://media.consumium.org [[w:GNU MediaGoblin]] | ||
== Subject-predicate-object database == | == Subject-predicate-object database == | ||
Revision as of 15:36, 26 August 2016
This article is about choice of database models and implementations.
Copyleft free to modify and free in cost software is strongly preferred over other solutions. Minimal modifications required could be another preference as that means maintenance of the chosen solution is minimized in that aspect.
Known types of databases
- Relational database provided by a RDBMS
- Subject-predicate-object database are provided by graph databases, specialized native triplestores and piggy-packing solutions that use an RDBMS to store and query the triplets and the networks they compose.
- Graph databases would intuitively appear more advanced than using RDF-triplet composed semantic networks.
- 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, a binary compatible drop-in replacement for MySQL that provides some technical advantages and the warm feeling that this is a fork of MySQL by the original MySQL AB founders.
- w:MySQL, the most widely known of free databases powering this Development Wiki
- w:PostgreSQL powering the https://media.consumium.org w:GNU MediaGoblin
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.