DBMS > Amazon DynamoDB vs. Apache Druid vs. PouchDB vs. RavenDB vs. SiteWhere

System Properties Comparison Amazon DynamoDB vs. Apache Druid vs. PouchDB vs. RavenDB vs. SiteWhere

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

M2M integration platform for persisting/querying time series data

Primary database model

Document store
Key-value store

Relational DBMS
Time Series DBMS

Document store

Time Series DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

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

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

aws.amazon.com/dynamodb

druid.apache.org

pouchdb.com

ravendb.net

github.com/sitewhere/sitewhere

Technical documentation

docs.aws.amazon.com/dynamodb

druid.apache.org/docs/latest/design

pouchdb.com/guides

ravendb.net/docs

sitewhere1.sitewhere.io/index.html

Developer

Amazon

Apache Software Foundation and contributors

Apache Software Foundation

Hibernating Rhinos

SiteWhere

Initial release

2012

2010

Current release

29.0.1, April 2024

7.1.1, June 2019

5.4, July 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache license v2

Open Source

AGPL version 3, commercial license available

Open Source

Common Public Attribution License Version 1.0

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

JavaScript

Java

Server operating systems

hosted

Linux
OS X
Unix

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

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-less columns are supported

schema-free

predefined scheme

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL for querying

SQL-like query language (RQL)

APIs and other access methods

RESTful HTTP API

JDBC
RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

HTTP REST

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

JavaScript

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

yes

Triggers

yes

by integration with AWS Lambda

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

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HDFS, S3 or other storage engines

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Multi-source replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Eventual Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID, Cluster-wide transaction available

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

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

Authorization levels configured per client per database

Users with fine-grained authorization concept

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.