DBMS > MySQL vs. Rockset vs. SpatiaLite vs. Teradata Aster vs. XTDB

System Properties Comparison MySQL vs. Rockset vs. SpatiaLite vs. Teradata Aster vs. XTDB

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

Widely used open source RDBMS

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Spatial extension of SQLite

Platform for big data analytics on multistructured data sources and types

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

Relational DBMS
Search engine

Relational DBMS

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.mysql.com

rockset.com

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

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

dev.mysql.com/doc

docs.rockset.com

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

www.xtdb.com/docs

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Rockset

Alessandro Furieri

Teradata

Juxt Ltd.

Initial release

1995

2019

2008

2005

2019

Current release

8.4.0, April 2024

5.0.0, August 2020

1.19, September 2021

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

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

commercial

Open Source

MIT License

Cloud-based only

Only available as a cloud service

yes

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

Clojure

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

hosted

server-less

Linux

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

yes

yes, extensible-data-notation format

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

ingestion from XML files supported

yes

in Aster File Store

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

with proprietary extensions

Read-only SQL queries, including JOINs

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

ADO.NET
JDBC
ODBC
OLE DB

HTTP REST
JDBC

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

Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Java
Python
R

Clojure
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

R packages

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Automatic sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

none

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Access rights for users and organizations can be defined via Rockset console

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.