DBMS > Apache IoTDB vs. BoltDB vs. Google Cloud Firestore vs. Heroic vs. Microsoft Azure Cosmos DB

System Properties Comparison Apache IoTDB vs. BoltDB vs. Google Cloud Firestore vs. Heroic vs. Microsoft Azure Cosmos DB

Editorial information provided by DB-Engines

Name

Description

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.

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.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

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

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

iotdb.apache.org

github.com/boltdb/bolt

firebase.google.com/products/firestore

github.com/spotify/heroic

azure.microsoft.com/services/cosmos-db

Technical documentation

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

firebase.google.com/docs/firestore

spotify.github.io/heroic

learn.microsoft.com/azure/cosmos-db

Developer

Apache Software Foundation

Google

Spotify

Microsoft

Initial release

2018

2013

2017

2014

Current release

1.1.0, April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

MIT License

commercial

Open Source

Apache 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

All OS with a Java VM (>= 1.8)

BSD
Linux
OS X
Solaris
Windows

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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 Elasticsearch

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

APIs and other access methods

JDBC
Native API

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

HQL (Heroic Query Language, a JSON-based language)
HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

yes, Firebase Rules & Cloud Functions

JavaScript

Triggers

yes

yes, with Cloud Functions

JavaScript

Partitioning methods

Methods for storing different data on different nodes

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

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

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

none

Multi-source replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Using Cloud Dataflow

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

Multi-item ACID transactions with snapshot isolation within a partition

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

yes

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

Access rights can be defined down to the item level

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.