DBMS > Apache Drill vs. Apache Druid vs. MySQL vs. RocksDB

System Properties Comparison Apache Drill vs. Apache Druid vs. MySQL vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Widely used open source RDBMS

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store
Relational DBMS

Relational DBMS
Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

Technical documentation

drill.apache.org/docs

druid.apache.org/docs/latest/design

dev.mysql.com/doc

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Apache Software Foundation and contributors

Oracle

since 2010, originally MySQL AB, then Sun

Facebook, Inc.

Initial release

2012

1995

2013

Current release

1.20.3, January 2023

29.0.1, April 2024

8.4.0, April 2024

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache license v2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

BSD

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

C++

Server operating systems

Linux
OS X
Windows

Linux
OS X
Unix

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

schema-less columns are supported

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL for querying

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

C++ API
Java API

Supported programming languages

C++

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

yes

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

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

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.