DBMS > Apache Druid vs. PostGIS vs. Quasardb vs. Riak TS vs. RocksDB

System Properties Comparison Apache Druid vs. PostGIS vs. Quasardb vs. Riak TS vs. RocksDB

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

Spatial extension of PostgreSQL

Distributed, high-performance timeseries database

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

Primary database model

Relational DBMS
Time Series DBMS

Spatial DBMS

Time Series DBMS

Key-value store

Secondary database models

Relational DBMS

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	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

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

Website

Technical documentation

druid.apache.org/docs/latest/design

postgis.net/documentation

doc.quasar.ai/master

www.tiot.jp/riak-docs/riak/ts/latest

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation and contributors

quasardb

Open Source, formerly Basho Technologies

Facebook, Inc.

Initial release

2012

2005

2009

2015

2013

Current release

29.0.1, April 2024

3.4.2, February 2024

3.14.1, January 2024

3.0.0, September 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

GPL v2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

Erlang

C++

Server operating systems

Linux
OS X
Unix

BSD
Linux
OS X
Windows

Linux
OS X

Linux

Data scheme

yes

schema-less columns are supported

yes

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

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

Secondary indexes

yes

with tags

restricted

SQL

Support of SQL

SQL for querying

yes

SQL-like query language

yes, limited

APIs and other access methods

JDBC
RESTful HTTP/JSON API

HTTP API

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

yes

based on PostgreSQL

Sharding

consistent hashing

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

based on PostgreSQL

Source-replica replication with selectable replication factor

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

yes

based on PostgreSQL

Cryptographically strong user authentication and audit trail

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.