DBMS > Apache Druid vs. Apache Impala vs. Heroic vs. MySQL

System Properties Comparison Apache Druid vs. Apache Impala vs. Heroic vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Analytic DBMS for Hadoop

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Widely used open source RDBMS

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

druid.apache.org

impala.apache.org

github.com/spotify/heroic

www.mysql.com

Technical documentation

druid.apache.org/docs/latest/design

impala.apache.org/impala-docs.html

spotify.github.io/heroic

dev.mysql.com/doc

Developer

Apache Software Foundation and contributors

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Spotify

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2013

2014

1995

Current release

29.0.1, April 2024

4.1.0, June 2022

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache Version 2

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Java

C++

Java

C and C++

Server operating systems

Linux
OS X
Unix

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-less columns are supported

yes

schema-free

yes

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL for querying

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

JDBC
RESTful HTTP/JSON API

JDBC
ODBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

All languages supporting JDBC/ODBC

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

selectable replication factor

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate 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

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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.