DBMS > EXASOL vs. IBM Db2 warehouse vs. MySQL vs. Riak TS

System Properties Comparison EXASOL vs. IBM Db2 warehouse vs. MySQL vs. Riak TS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Cloud-based data warehousing service

Widely used open source RDBMS

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.66
Rank	#138	Overall
	#64	Relational DBMS

Score	1.26
Rank	#162	Overall
	#73	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Website

www.exasol.com

www.ibm.com/products/db2/warehouse

www.mysql.com

Technical documentation

www.exasol.com/resources

dev.mysql.com/doc

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Exasol

IBM

Oracle

since 2010, originally MySQL AB, then Sun

Open Source, formerly Basho Technologies

Initial release

2000

2014

1995

2015

Current release

9.0.0, July 2024

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

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.

Implementation language

C and C++

Erlang

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X

Data scheme

yes

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.

Import/export of XML data possible

yes

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

with proprietary extensions

yes, limited

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Native Erlang Interface

Supported programming languages

Java
Lua
Python
R

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

PL/SQL, SQL PL

yes

proprietary syntax

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

links between datasets can be stored

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

Access rights for users, groups and roles according to SQL-standard

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or 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.