DBMS > MariaDB vs. OrigoDB vs. Tarantool vs. TerarkDB

System Properties Comparison MariaDB vs. OrigoDB vs. Tarantool vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

A fully ACID in-memory object graph database

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Document store
Key-value store
Relational DBMS

Key-value store

Secondary database models

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

origodb.com

www.tarantool.io

github.com/bytedance/terarkdb

Technical documentation

mariadb.com/kb/en/library

origodb.com/docs

www.tarantool.io/en/doc

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

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

The lead developer Monty Widenius is the original author of MySQL

Robert Friberg et al

ByteDance, originally Terark

Initial release

2009

Fork of MySQL, which was first released in 1995

2009

under the name LiveDB

2008

2016

Current release

11.3.2, February 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

GPL version 2, commercial enterprise subscription available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

commercial

restricted open source version available

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.

Implementation language

C and C++

C++

Server operating systems

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

Linux
Windows

BSD
Linux
macOS

Data scheme

yes

Dynamic columns are supported

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

string, double, decimal, uuid, integer, blob, boolean, datetime

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

Full-featured ANSI SQL support

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP API
LINQ

Open binary protocol

C++ API
Java 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

.Net

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

C++
Java

Server-side scripts

Stored procedures

yes

PL/SQL compatibility added with version 10.3

yes

Lua, C and SQL stored procedures

Triggers

yes

Domain Events

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

several options for horizontal partitioning and Sharding

horizontal partitioning

client side managed; servers are not synchronized

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

depending on model

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

not for in-memory storage engine

yes

Write ahead log

yes, write ahead 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

yes

yes, full featured in-memory storage engine with persistence

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role based authorization

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

More information provided by the system vendor

Specific characteristics

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

Competitive advantages

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

Typical application scenarios

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

Key customers

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

Market metrics

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

Licensing and pricing models

MariaDB plc subscriptions cover our free, open source database, Community Server,...
» 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.