DBMS > Apache Druid vs. etcd vs. RocksDB vs. Rockset vs. searchxml

System Properties Comparison Apache Druid vs. etcd vs. RocksDB vs. Rockset vs. searchxml

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 distributed reliable key-value store

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

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Relational DBMS
Time Series DBMS

Key-value store

Document store

Native XML DBMS
Search engine

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	7.25
Rank	#54	Overall
	#5	Key-value stores

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

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

druid.apache.org

etcd.io
github.com/etcd-io/etcd

rocksdb.org

rockset.com

www.searchxml.net/category/products

Technical documentation

druid.apache.org/docs/latest/design

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

github.com/facebook/rocksdb/wiki

docs.rockset.com

www.searchxml.net/support/handouts

Developer

Apache Software Foundation and contributors

Facebook, Inc.

Rockset

informationpartners gmbh

Initial release

2012

2013

2019

2015

Current release

29.0.1, April 2024

3.4, August 2019

8.11.4, April 2024

1.0

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache Version 2.0

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

C++

Server operating systems

Linux
OS X
Unix

FreeBSD
Linux
Windows

experimental

Linux

hosted

Windows

Data scheme

yes

schema-less columns are supported

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

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.

ingestion from XML files supported

yes

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL for querying

Read-only SQL queries, including JOINs

APIs and other access methods

JDBC
RESTful HTTP/JSON API

gRPC
JSON over HTTP

C++ API
Java API

HTTP REST

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

yes

on the application server

Triggers

yes, watching key changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

horizontal partitioning

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

multiple readers, single writer

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

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 organizations can be defined via Rockset console

Domain, group and role-based access control at the document level and for application services

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.