DBMS > Apache Druid vs. HarperDB vs. PouchDB vs. Snowflake vs. STSdb

System Properties Comparison Apache Druid vs. HarperDB vs. PouchDB vs. Snowflake vs. STSdb

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

JavaScript DBMS with an API inspired by CouchDB

Cloud-based data warehousing service for structured and semi-structured data

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS
Time Series DBMS

Document store

Relational DBMS

Key-value store

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

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Website

github.com/STSSoft/STSdb4

Technical documentation

druid.apache.org/docs/latest/design

docs.harperdb.io/docs

pouchdb.com/guides

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation and contributors

HarperDB

Apache Software Foundation

Snowflake Computing Inc.

STS Soft SC

Initial release

2012

2017

2012

2014

2011

Current release

29.0.1, April 2024

3.1, August 2021

7.1.1, June 2019

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache license v2

commercial

free community edition available

Open Source

commercial

Open Source

GPLv2, commercial license available

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

Node.js

JavaScript

Server operating systems

Linux
OS X
Unix

Linux
OS X

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

hosted

Windows

Data scheme

yes

schema-less columns are supported

dynamic schema

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

yes

JSON data types

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.

yes

Secondary indexes

yes

via views

SQL

Support of SQL

SQL for querying

SQL-like data manipulation statements

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

HTTP REST

only for PouchDB Server
JavaScript API

CLI Client
JDBC
ODBC

.NET Client API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

JavaScript

JavaScript (Node.js)
Python

C#
Java

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

View functions in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

A table resides as a whole on one (or more) nodes in a cluster

Sharding

with a proxy-based framework, named couchdb-lounge

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

the nodes on which a table resides can be defined

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

none

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

Access rights for users and roles

Users with fine-grained authorization concept, user roles and pluggable authentication

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.