DBMS > MySQL vs. SpatiaLite vs. Sqrrl vs. Tarantool vs. Trafodion

System Properties Comparison MySQL vs. SpatiaLite vs. Sqrrl vs. Tarantool vs. Trafodion

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

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

Description

Widely used open source RDBMS

Spatial extension of SQLite

Adaptable, secure NoSQL built on Apache Accumulo

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

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

Website

www.mysql.com

www.gaia-gis.it/fossil/libspatialite/index

sqrrl.com

www.tarantool.io

trafodion.apache.org

Technical documentation

dev.mysql.com/doc

www.gaia-gis.it/gaia-sins/spatialite_topics.html

www.tarantool.io/en/doc

trafodion.apache.org/documentation.html

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Alessandro Furieri

Amazon

originally Sqrrl Data, Inc.

Apache Software Foundation, originally developed by HP

Initial release

1995

2008

2012

2008

2014

Current release

8.4.0, April 2024

5.0.0, August 2020

2.10.0, May 2022

2.3.0, February 2019

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

commercial

Open Source

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

Open Source

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

Java

C and C++

C++, Java

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

server-less

Linux

BSD
Linux
macOS

Linux

Data scheme

yes

schema-free

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

yes

Typing

predefined data types such as float or date

yes

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

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

yes

with proprietary extensions

yes

Full-featured ANSI SQL support

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Open binary protocol

ADO.NET
JDBC
ODBC

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

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

proprietary syntax

Lua, C and SQL stored procedures

Java 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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Sharding

making use of Hadoop

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

selectable replication factor

making use of Hadoop

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

yes, via HBase

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

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

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

Atomic updates per row, document, or graph entity

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

ACID

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

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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

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.