DBMS > Apache Druid vs. RocksDB vs. RRDtool vs. SAP Adaptive Server

System Properties Comparison Apache Druid vs. RocksDB vs. RRDtool vs. SAP Adaptive Server

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

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

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Primary database model

Relational DBMS
Time Series DBMS

Key-value store

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

with Boeing's Spatial Query Server

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	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Website

druid.apache.org

rocksdb.org

oss.oetiker.ch/rrdtool

www.sap.com/products/technology-platform/sybase-ase.html

Technical documentation

druid.apache.org/docs/latest/design

github.com/facebook/rocksdb/wiki

oss.oetiker.ch/rrdtool/doc

help.sap.com/docs/SAP_ASE

Developer

Apache Software Foundation and contributors

Facebook, Inc.

Tobias Oetiker

SAP, Sybase

Initial release

2012

2013

1999

1987

Current release

29.0.1, April 2024

8.11.4, April 2024

1.8.0, 2022

16.0

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

BSD

Open Source

GPL V2 and FLOSS

commercial

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

Implementations in Java (e.g. RRD4J) and C# available

C and C++

Server operating systems

Linux
OS X
Unix

Linux

HP-UX
Linux

AIX
HP-UX
Linux
Solaris
Unix
Windows

Data scheme

yes

schema-less columns are supported

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

C++ API
Java API

in-process shared library
Pipes

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

C
C++
Cobol
Java
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

Java and Transact-SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

horizontal partitioning

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

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

fine grained access rights according to SQL-standard

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.