DBMS > GraphDB vs. Interbase vs. MariaDB vs. Microsoft Access vs. ToroDB

System Properties Comparison GraphDB vs. Interbase vs. MariaDB vs. Microsoft Access vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Enterprise-ready RDF and graph database with efficient reasoning, cluster and external index synchronization support. It supports also SQL JDBC access to Knowledge Graph and GraphQL over SPARQL.

Light-weight proven RDBMS

originally from Borland

MySQL application compatible open source RDBMS, enhanced with high availability, security, interoperability and performance capabilities. MariaDB ColumnStore provides a column-oriented storage engine and MariaDB Xpand supports distributed SQL.

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Graph DBMS
RDF store

Relational DBMS

Document store

Secondary database models

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	3.25
Rank	#91	Overall
	#7	Graph DBMS
	#4	RDF stores

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	91.04
Rank	#13	Overall
	#9	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Website

www.ontotext.com

www.embarcadero.com/products/interbase

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

www.microsoft.com/en-us/microsoft-365/access

github.com/torodb/server

Technical documentation

graphdb.ontotext.com/documentation

docs.embarcadero.com/products/interbase

mariadb.com/kb/en/library

developer.microsoft.com/en-us/access

Social network pages

Developer

Ontotext

Embarcadero

MariaDB Corporation Ab (MariaDB Enterprise),
MariaDB Foundation (community MariaDB Server)

The lead developer Monty Widenius is the original author of MySQL

Microsoft

8Kdata

Initial release

2000

1984

2009

Fork of MySQL, which was first released in 1995

1992

2016

Current release

10.4, October 2023

InterBase 2020, December 2019

11.3.2, February 2024

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Some plugins of GraphDB Workbench are open sourced

commercial

Open Source

GPL version 2, commercial enterprise subscription available

commercial

Bundled with Microsoft Office

Open Source

AGPL-V3

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

STACKIT MariaDB offers MariaDB in a fully managed version in enterprise grade, 100% GDPR-compliant.

Implementation language

Java

C and C++

C++

Java

Server operating systems

All OS with a Java VM
Linux
OS X
Windows

Android
iOS
Linux
OS X
Windows

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

Windows

Not a real database server, but making use of DLLs

All OS with a Java 7 VM

Data scheme

schema-free and OWL/RDFS-schema support; RDF shapes

yes

Dynamic columns are supported

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

export as XML data possible

yes

Secondary indexes

yes, supports real-time synchronization and indexing in SOLR/Elastic search/Lucene and GeoSPARQL geometry data indexes

yes

SQL

Support of SQL

stored SPARQL accessed as SQL using Apache Calcite through JDBC/ODBC

yes

with proprietary extensions

yes

but not compliant to any SQL standard

APIs and other access methods

GeoSPARQL
GraphQL
GraphQL Federation
Java API
JDBC
RDF4J API
RDFS
RIO
Sail API
Sesame REST HTTP Protocol
SPARQL 1.1

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

.Net
C#
Clojure
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

Ada
C
C#
C++
D
Eiffel
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

Server-side scripts

Stored procedures

well-defined plugin interfaces; JavaScript server-side extensibility

yes

Interbase procedure and trigger language

yes

PL/SQL compatibility added with version 10.3

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

none

several options for horizontal partitioning and Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Interbase Change Views

Multi-source replication
Source-replica replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency, Eventual consistency (configurable in cluster mode per master or individual client request)

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Constraint checking

yes

not for MyISAM storage engine

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

not for MyISAM storage engine

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

not for in-memory storage engine

yes

but no files for transaction logging

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

with MEMORY storage engine

User concepts

Access control

Default Basic authentication through RDF4J client, or via Java when run with cURL, default token-based in the Workbench or via Rest API, optional access through OpenID or Kerberos single sign-on.

fine grained access rights according to SQL-standard

a simple user-level security was built in till version Access 2003

Access rights for users and roles

More information provided by the system vendor

Specific characteristics

Ontotext GraphDB is a semantic database engine that allows organizations to build...
» more

MariaDB is the most powerful open source relational database – modern SQL and JSON...
» more

Competitive advantages

GraphDB allows you to link text and data in big knowledge graphs. It’s easy to experiment...
» more

MariaDB Servers have many features unavailable in other open source relational databases....
» more

Typical application scenarios

Metadata enrichment and management, linked data publishing, semantic inferencing...
» more

Web, SaaS and Cloud operational applications that require high availability, scalability...
» more

Key customers

GraphDB provides a platform for building next-generation AI and Knowledge Graph...
» more

Deutsche Bank, DBS Bank, Nasdaq, Red Hat, ServiceNow, Verizon and Walgreens Featured...
» more

Market metrics

GraphDB is the most utilized semantic triplestore for mission-critical enterprise...
» more

MariaDB is the default database in the LAMP stack supplied by Red Hat and SUSE Linux,...
» more

Licensing and pricing models

GraphDB Free is a non-commercial version and is free to use. GraphDB Enterprise edition...
» more

MariaDB plc subscriptions cover our free, open source database, Community Server,...
» more

News

Riding the Databricks Wave with Hybrid Knowledge Graphs
6 June 2024

Matching Skills and Candidates with Graph RAG
31 May 2024

A Triple Store RAG Retriever
29 May 2024

Integrating GraphDB with Relational Database Systems
23 May 2024

Understanding the Graph Center of Excellence
17 May 2024

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.