DBMS > Apache Druid vs. IBM Cloudant vs. OpenQM vs. RocksDB vs. Rockset

System Properties Comparison Apache Druid vs. IBM Cloudant vs. OpenQM vs. RocksDB vs. Rockset

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

Database as a Service offering based on Apache CouchDB

QpenQM is a high-performance, self-tuning, multi-value DBMS

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

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Relational DBMS
Time Series DBMS

Secondary database models

Relational DBMS
Search engine

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

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

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

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

Score	0.79
Rank	#211	Overall
	#35	Document stores

Website

druid.apache.org

www.ibm.com/products/cloudant

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

rocksdb.org

rockset.com

Technical documentation

druid.apache.org/docs/latest/design

cloud.ibm.com/docs/Cloudant

github.com/facebook/rocksdb/wiki

docs.rockset.com

Developer

Apache Software Foundation and contributors

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Rocket Software, originally Martin Phillips

Facebook, Inc.

Rockset

Initial release

2012

2010

1993

2013

2019

Current release

29.0.1, April 2024

3.4-12

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

GPLv2, extended commercial license available

Open Source

BSD

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Erlang

C++

Server operating systems

Linux
OS X
Unix

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux

hosted

Data scheme

yes

schema-less columns are supported

schema-free

yes

with some exceptions

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

SQL for querying

Read-only SQL queries, including JOINs

APIs and other access methods

JDBC
RESTful HTTP/JSON API

RESTful HTTP/JSON API

C++ API
Java API

HTTP REST

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
Basic
C
Java
Objective C
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

yes

horizontal partitioning

Automatic sharding

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

Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a document possible

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

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 can be defined per database

Access rights can be defined down to the item level

Access rights for users and organizations can be defined via Rockset console

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.