DBMS > Apache Druid vs. Oracle NoSQL vs. RocksDB vs. Warp 10

System Properties Comparison Apache Druid vs. Oracle NoSQL vs. RocksDB vs. Warp 10

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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS
Time Series DBMS

Document store
Key-value store
Relational DBMS

Key-value store

Time Series DBMS

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

Score	3.29
Rank	#95	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

Score	2.96
Rank	#103	Overall
	#18	Document stores
	#17	Key-value stores
	#52	Relational DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	0.08
Rank	#358	Overall
	#35	Time Series DBMS

Website

druid.apache.org

www.oracle.com/database/nosql/technologies/nosql

rocksdb.org

www.warp10.io

Technical documentation

druid.apache.org/docs/latest/design

docs.oracle.com/en/database/other-databases/nosql-database/index.html

github.com/facebook/rocksdb/wiki

www.warp10.io/content/02_Getting_started

Developer

Apache Software Foundation and contributors

Oracle

Facebook, Inc.

SenX

Initial release

2012

2011

2013

2015

Current release

29.0.1, April 2024

23.3, December 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

BSD

Open Source

Apache License 2.0

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

Java

Server operating systems

Linux
OS X
Unix

Linux
Solaris SPARC/x86

Linux

Linux
OS X
Windows

Data scheme

yes

schema-less columns are supported

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

schema-free

Typing

predefined data types such as float or date

yes

optional

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.

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

SQL-like DML and DDL statements

APIs and other access methods

JDBC
RESTful HTTP/JSON API

RESTful HTTP API

C++ API
Java API

HTTP API
Jupyter
WebSocket

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C
C#
Go
Java
JavaScript (Node.js)
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

WarpScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

Transaction concepts

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

configurable

ACID within a storage node (=shard)

yes

Concurrency

Support for concurrent manipulation of data

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

off heap cache

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 and roles

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.