DBMS > Apache Druid vs. PouchDB vs. RocksDB vs. STSdb vs. VictoriaMetrics

System Properties Comparison Apache Druid vs. PouchDB vs. RocksDB vs. STSdb vs. VictoriaMetrics

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

JavaScript DBMS with an API inspired by CouchDB

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Relational DBMS
Time Series DBMS

Document store

Key-value store

Time Series 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	2.28
Rank	#115	Overall
	#21	Document stores

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

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

druid.apache.org

pouchdb.com

rocksdb.org

github.com/STSSoft/STSdb4

victoriametrics.com

Technical documentation

druid.apache.org/docs/latest/design

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Apache Software Foundation and contributors

Apache Software Foundation

Facebook, Inc.

STS Soft SC

VictoriaMetrics

Initial release

2012

2013

2011

2018

Current release

29.0.1, April 2024

7.1.1, June 2019

8.11.4, April 2024

4.0.8, September 2015

v1.91, May 2023

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

BSD

Open Source

GPLv2, commercial license available

Open Source

Apache Version 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

JavaScript

C++

Server operating systems

Linux
OS X
Unix

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Windows

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

schema-less columns are supported

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

via views

SQL

Support of SQL

SQL for querying

APIs and other access methods

JDBC
RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

.NET Client API

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

C#
Java

Server-side scripts

Stored procedures

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

none

Synchronous replication

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

Foreign keys

Referential integrity

Transaction concepts

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

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.