DBMS > Amazon DynamoDB vs. Apache IoTDB vs. Firebase Realtime Database vs. JanusGraph vs. Riak TS

System Properties Comparison Amazon DynamoDB vs. Apache IoTDB vs. Firebase Realtime Database vs. JanusGraph vs. Riak TS

Editorial information provided by DB-Engines

Name

Description

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

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

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

Primary database model

Document store
Key-value store

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	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

aws.amazon.com/dynamodb

iotdb.apache.org

firebase.google.com/products/realtime-database

janusgraph.org

Technical documentation

docs.aws.amazon.com/dynamodb

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

firebase.google.com/docs/database

docs.janusgraph.org

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

Developer

Amazon

Apache Software Foundation

Google

acquired by Google 2014

Linux Foundation; originally developed as Titan by Aurelius

Open Source, formerly Basho Technologies

Initial release

2012

2018

2012

2017

2015

Current release

1.1.0, April 2023

0.6.3, February 2023

3.0.0, September 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0

Open Source

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

Erlang

Server operating systems

hosted

All OS with a Java VM (>= 1.8)

hosted

Linux
OS X
Unix
Windows

Linux
OS X

Data scheme

schema-free

yes

schema-free

yes

schema-free

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

restricted

SQL

Support of SQL

SQL-like query language

yes, limited

APIs and other access methods

RESTful HTTP API

JDBC
Native API

Android
iOS
JavaScript API
RESTful HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

HTTP API
Native Erlang Interface

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
C++
Go
Java
Python
Scala

Java
JavaScript
Objective-C

Clojure
Java
Python

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

yes

limited functionality with using 'rules'

yes

Erlang

Triggers

yes

by integration with AWS Lambda

yes

Callbacks are triggered when data changes

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

yes

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Integration with Hadoop and Spark

yes

via Faunus, a graph analytics engine

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency
Strong Consistency with Raft

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

links between datasets 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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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)

yes

yes, based on authentication and database rules

User authentification and security via Rexster Graph Server

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.