DBMS > ArcadeDB vs. MySQL vs. OpenMLDB vs. TerarkDB

System Properties Comparison ArcadeDB vs. MySQL vs. OpenMLDB vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

Widely used open source RDBMS

An open-source machine learning database that provides a feature platform for training and inference

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

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	0.02
Rank	#374	Overall
	#52	Document stores
	#38	Graph DBMS
	#56	Key-value stores
	#38	Time Series DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.11
Rank	#339	Overall
	#30	Time Series DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

arcadedb.com

www.mysql.com

openmldb.ai

github.com/bytedance/terarkdb

Technical documentation

docs.arcadedb.com

dev.mysql.com/doc

openmldb.ai/docs/zh/main

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Arcade Data

Oracle

since 2010, originally MySQL AB, then Sun

4 Paradigm Inc.

ByteDance, originally Terark

Initial release

2021

1995

2020

2016

Current release

September 2021

9.0.0, July 2024

2024-2 February 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

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

Java

C and C++

C++, Java, Scala

C++

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

Fixed schema

schema-free

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

SQL

Support of SQL

SQL-like query language, no joins

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
SQLAlchemy

C++ API
Java API

Supported programming languages

Java

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

C++
Go
Java
Python
Scala

C++
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

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 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

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.