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

System Properties Comparison Apache Drill vs. Apache Druid vs. KeyDB 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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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

Primary database model

Document store
Relational DBMS

Relational DBMS
Time Series DBMS

Key-value store

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	0.71
Rank	#226	Overall
	#33	Key-value stores

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

Website

drill.apache.org

druid.apache.org

github.com/Snapchat/KeyDB
keydb.dev

rocksdb.org

Technical documentation

drill.apache.org/docs

druid.apache.org/docs/latest/design

docs.keydb.dev

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Apache Software Foundation and contributors

EQ Alpha Technology Ltd.

Facebook, Inc.

Initial release

2012

2019

2013

Current release

1.20.3, January 2023

29.0.1, April 2024

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache license v2

Open Source

BSD-3

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.

Implementation language

Java

C++

Server operating systems

Linux
OS X
Windows

Linux
OS X
Unix

Linux

Data scheme

schema-free

yes

schema-less columns are supported

schema-free

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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.

Secondary indexes

yes

by using the Redis Search module

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL for querying

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
RESTful HTTP/JSON API

Proprietary protocol

RESP - REdis Serialization Protoco

C++ API
Java API

Supported programming languages

C++

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

Lua

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

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

Eventual Consistency
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

simple password-based access control and ACL

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.