DBMS > AgensGraph vs. AlaSQL vs. MySQL vs. SAP SQL Anywhere vs. Tarantool

System Properties Comparison AgensGraph vs. AlaSQL vs. MySQL vs. SAP SQL Anywhere vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

JavaScript DBMS library

Widely used open source RDBMS

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

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

Primary database model

Graph DBMS
Relational DBMS

Document store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

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

Website

bitnine.net/agensgraph

alasql.org

www.mysql.com

www.sap.com/products/technology-platform/sql-anywhere.html

www.tarantool.io

Technical documentation

bitnine.net/documentation

github.com/AlaSQL/alasql

dev.mysql.com/doc

help.sap.com/docs/SAP_SQL_Anywhere

www.tarantool.io/en/doc

Developer

Bitnine Global Inc.

Andrey Gershun & Mathias R. Wulff

Oracle

since 2010, originally MySQL AB, then Sun

SAP

formerly Sybase

Initial release

2016

2014

1995

1992

2008

Current release

2.1, December 2018

8.4.0, April 2024

17, July 2015

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

MIT-License

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

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

JavaScript

C and C++

Server operating systems

Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

BSD
Linux
macOS

Data scheme

depending on used data model

schema-free

yes

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

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

Close to SQL99, but no user access control, stored procedures and host language bindings.

yes

with proprietary extensions

yes

Full-featured ANSI SQL support

APIs and other access methods

Cypher Query Language
JDBC

JavaScript API

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
HTTP API
JDBC
ODBC

Open binary protocol

Supported programming languages

C
Java
JavaScript
Python

JavaScript

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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

yes

proprietary syntax

yes, in C/C++, Java, .Net or Perl

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

no, but can be realized using table inheritance

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.

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication
Source-replica replication

Source-replica replication

Database mirroring

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

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

yes

Transaction concepts

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

ACID

yes

only for local storage and DOM-storage

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

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

fine grained access rights according to SQL-standard

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.