DBMS > MySQL vs. RDF4J vs. Teradata Aster vs. TigerGraph vs. Trafodion

System Properties Comparison MySQL vs. RDF4J vs. Teradata Aster vs. TigerGraph vs. Trafodion

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Widely used open source RDBMS

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Platform for big data analytics on multistructured data sources and types

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

Technical documentation

dev.mysql.com/doc

rdf4j.org/documentation

docs.tigergraph.com

trafodion.apache.org/documentation.html

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Teradata

Apache Software Foundation, originally developed by HP

Initial release

1995

2004

2005

2017

2014

Current release

8.4.0, April 2024

2.3.0, February 2019

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Open Source

Apache 2.0

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Java

C++

C++, Java

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Unix
Windows

Linux

Data scheme

yes

RDF Schemas

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

yes

Typing

predefined data types such as float or date

yes

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.

yes

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-like query language (GSQL)

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

ADO.NET
JDBC
ODBC
OLE DB

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

Supported programming languages

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

Java
PHP
Python

C
C#
C++
Java
Python
R

C++
Java

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

R packages

yes

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

Role-based access control

fine grained access rights according to SQL-standard

More information provided by the system vendor

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.