DBMS > Apache Impala vs. EventStoreDB vs. EXASOL vs. MySQL vs. RRDtool

System Properties Comparison Apache Impala vs. EventStoreDB vs. EXASOL vs. MySQL vs. RRDtool

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Industrial-strength, open-source database solution built from the ground up for event sourcing.

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

Widely used open source RDBMS

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Primary database model

Relational DBMS

Event Store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	1.10
Rank	#179	Overall
	#1	Event Stores

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Website

oss.oetiker.ch/rrdtool

Technical documentation

impala.apache.org/impala-docs.html

developers.eventstore.com

www.exasol.com/resources

dev.mysql.com/doc

oss.oetiker.ch/rrdtool/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Event Store Limited

Exasol

Oracle

since 2010, originally MySQL AB, then Sun

Tobias Oetiker

Initial release

2013

2012

2000

1995

1999

Current release

4.1.0, June 2022

21.2, February 2021

8.4.0, April 2024

1.8.0, 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V2 and FLOSS

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

C and C++

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

Linux

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

HP-UX
Linux

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

ADO.NET
JDBC
ODBC
Proprietary native API

in-process shared library
Pipes

Supported programming languages

All languages supporting JDBC/ODBC

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

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

none

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

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

by using the rrdcached daemon

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

based on Apache Sentry and Kerberos

Access rights for users, groups and roles 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.