DBMS > Dolt vs. MySQL vs. SAP Advantage Database Server vs. Tarantool vs. Tkrzw

System Properties Comparison Dolt vs. MySQL vs. SAP Advantage Database Server vs. Tarantool vs. Tkrzw

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

Widely used open source RDBMS

Low-cost RDBMS with access to ISAM and FoxPro data structures

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Document store
Key-value store
Relational DBMS

Key-value store

Secondary database models

Document store

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

github.com/dolthub/dolt
www.dolthub.com

www.mysql.com

www.sap.com/products/advantage-database-server.html

www.tarantool.io

dbmx.net/tkrzw

Technical documentation

docs.dolthub.com

dev.mysql.com/doc

www.tarantool.io/en/doc

Developer

DoltHub Inc

Oracle

since 2010, originally MySQL AB, then Sun

Sybase, SAP

Mikio Hirabayashi

Initial release

2018

1995

1993

2008

2020

Current release

8.4.0, April 2024

2.10.0, May 2022

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

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

Open Source

Apache Version 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++

C++

Server operating systems

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

BSD
Linux
macOS

Linux
macOS

Data scheme

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

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

Full-featured ANSI SQL support

APIs and other access methods

CLI Client
HTTP REST

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Open binary protocol

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

Delphi
Perl
PHP

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

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

proprietary syntax

yes

Lua, C and SQL stored procedures

Triggers

yes

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

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

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

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication
Source-replica replication

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
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

Immediate Consistency

Foreign keys

Referential integrity

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

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

table locks or row locks depending on storage engine

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

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

caching of (temporary) tables can be configured

yes, full featured in-memory storage engine with persistence

yes

using specific database classes

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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

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.