DBMS > Amazon DynamoDB vs. Apache IoTDB vs. BoltDB vs. Dolt vs. Google Cloud Firestore

System Properties Comparison Amazon DynamoDB vs. Apache IoTDB vs. BoltDB vs. Dolt vs. Google Cloud Firestore

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

An embedded key-value store for Go.

A MySQL compatible DBMS with Git-like versioning of data and schema

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Primary database model

Document store
Key-value store

Secondary database models

Document store

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

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Website

aws.amazon.com/dynamodb

iotdb.apache.org

github.com/boltdb/bolt

github.com/dolthub/dolt
www.dolthub.com

firebase.google.com/products/firestore

Technical documentation

docs.aws.amazon.com/dynamodb

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

docs.dolthub.com

firebase.google.com/docs/firestore

Developer

Amazon

Apache Software Foundation

DoltHub Inc

Google

Initial release

2012

2018

2013

2018

2017

Current release

1.1.0, April 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

Open Source

MIT License

Open Source

Apache Version 2.0

commercial

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

Server operating systems

hosted

All OS with a Java VM (>= 1.8)

BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

hosted

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

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

JDBC
Native API

CLI Client
HTTP REST

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
C++
Go
Java
Python
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

yes, Firebase Rules & Cloud Functions

Triggers

yes

by integration with AWS Lambda

yes

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

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

none

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Integration with Hadoop and Spark

Using Cloud Dataflow

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

none

Immediate Consistency

Foreign keys

Referential integrity

yes

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Only one user is configurable, and must be specified in the config file at startup

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

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.