DBMS > MariaDB vs. RDF4J vs. ScyllaDB vs. Trafodion vs. VoltDB

System Properties Comparison MariaDB vs. RDF4J vs. ScyllaDB vs. Trafodion vs. VoltDB

Editorial information provided by DB-Engines

Name

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

Description

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.

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

Cassandra and DynamoDB compatible wide column store

Transactional SQL-on-Hadoop DBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Secondary database models

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

Key-value store

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

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	4.75
Rank	#68	Overall
	#5	Wide column stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

Technical documentation

mariadb.com/kb/en/library

rdf4j.org/documentation

docs.scylladb.com

trafodion.apache.org/documentation.html

docs.voltdb.com

Developer

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

The lead developer Monty Widenius is the original author of MySQL

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

ScyllaDB

Apache Software Foundation, originally developed by HP

VoltDB Inc.

Initial release

2009

Fork of MySQL, which was first released in 1995

2004

2015

2014

2010

Current release

11.3.2, February 2024

ScyllaDB Open Source 5.4.1, January 2024

2.3.0, February 2019

11.3, April 2022

License

Commercial or Open Source

Open Source

GPL version 2, commercial enterprise subscription available

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Open Source (AGPL), commercial license available

Open Source

Apache 2.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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.

Scylla Cloud: Create real-time applications that run at global scale with Scylla Cloud, the industry’s most powerful NoSQL DBaaS

Implementation language

C and C++

Java

C++

C++, Java

Java, C++

Server operating systems

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

Linux
OS X
Unix
Windows

Linux

Linux
OS X

for development

Data scheme

yes

Dynamic columns are supported

yes

RDF Schemas

schema-free

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

Secondary indexes

yes

cluster global secondary indices

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like DML and DDL statements (CQL)

yes

only a subset of SQL 99

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

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

ADO.NET
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

Java
PHP
Python

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

PL/SQL compatibility added with version 10.3

yes

yes, Lua

Java Stored Procedures

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

several options for horizontal partitioning and Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

selectable replication factor

Representation of geographical distribution of servers is possible

yes, via HBase

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

FOREIGN KEY constraints are not supported

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

Atomicity and isolation are supported for single operations

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

not for in-memory storage engine

yes

in-memory storage is supported as well

yes

Snapshots and command logging

In-memory capabilities

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

yes

with MEMORY storage engine

yes

in-memory tables

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per object

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

More information provided by the system vendor

Specific characteristics

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

ScyllaDB is engineered to deliver predictable performance at scale. It’s adopted...
» more

Competitive advantages

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

Highly-performant (efficiently utilizes full resources of a node and network; millions...
» more

Typical application scenarios

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

ScyllaDB is ideal for applications that require high throughput and low latency at...
» more

Key customers

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

Discord, Epic Games, Expedia, Zillow, Comcast, Disney+ Hotstar, Samsung, ShareChat,...
» more

Market metrics

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

ScyllaDB typically offers ~75% total cost of ownership savings, with ~5X higher throughput...
» more

Licensing and pricing models

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

ScyllaDB Open Source - free open source software (AGPL) ScyllaDB Enterprise - subscription-based...
» more

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.