DBMS > Amazon DynamoDB vs. Quasardb vs. Riak KV vs. SiteWhere

System Properties Comparison Amazon DynamoDB vs. Quasardb vs. Riak KV vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Distributed, high-performance timeseries database

Distributed, fault tolerant key-value store

M2M integration platform for persisting/querying time series data

Primary database model

Document store
Key-value store

Time Series DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Time Series DBMS

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

Score	77.57
Rank	#16	Overall
	#2	Document stores
	#2	Key-value stores

Score	0.19
Rank	#327	Overall
	#30	Time Series DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Score	0.06
Rank	#367	Overall
	#36	Time Series DBMS

Website

aws.amazon.com/dynamodb

quasar.ai

github.com/sitewhere/sitewhere

Technical documentation

docs.aws.amazon.com/dynamodb

doc.quasar.ai/master

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

sitewhere1.sitewhere.io/index.html

Developer

Amazon

quasardb

OpenSource, formerly Basho Technologies

SiteWhere

Initial release

2012

2009

2010

Current release

3.14.1, January 2024

3.2.0, December 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

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

Open Source

Apache version 2, commercial enterprise edition

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

C++

Erlang

Java

Server operating systems

hosted

BSD
Linux
OS X
Windows

Linux
OS X

Linux
OS X
Windows

Data scheme

schema-free

predefined scheme

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

restricted

SQL

Support of SQL

SQL-like query language

APIs and other access methods

RESTful HTTP API

HTTP API

HTTP API
Native Erlang Interface

HTTP REST

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.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

Server-side scripts

Stored procedures

Erlang

Triggers

yes

by integration with AWS Lambda

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

Sharding

no "single point of failure"

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication with selectable replication factor

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)

with Hadoop integration

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

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

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

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

User concepts

Access control

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

Cryptographically strong user authentication and audit trail

yes, using Riak Security

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.