DBMS > EXASOL vs. MySQL vs. RavenDB vs. Rockset

System Properties Comparison EXASOL vs. MySQL vs. RavenDB vs. Rockset

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.

Widely used open source RDBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Primary database model

Relational DBMS

Key/Value like access via memcached API

Document store

Secondary database models

Document store
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

Relational DBMS
Search engine

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

Score	1.66
Rank	#138	Overall
	#64	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	2.68
Rank	#102	Overall
	#19	Document stores

Score	1.07
Rank	#180	Overall
	#31	Document stores

Website

Technical documentation

www.exasol.com/resources

dev.mysql.com/doc

ravendb.net/docs

docs.rockset.com

Developer

Exasol

Oracle

since 2010, originally MySQL AB, then Sun

Hibernating Rhinos

Rockset

Initial release

2000

1995

2010

2019

Current release

9.0.0, July 2024

5.4, July 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL version 3, commercial license available

commercial

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

C++

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

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

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (RQL)

Read-only SQL queries, including JOINs

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

HTTP REST

Supported programming languages

Java
Lua
Python
R

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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

yes

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

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID, Cluster-wide transaction available

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

Users with fine-grained authorization concept

no user groups or roles

Authorization levels configured per client per database

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

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.