DBMS > Apache IoTDB vs. ClickHouse vs. Google Cloud Datastore vs. Google Cloud Firestore vs. Heroic

System Properties Comparison Apache IoTDB vs. ClickHouse vs. Google Cloud Datastore vs. Google Cloud Firestore vs. Heroic

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

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

Primary database model

Secondary database models

Time Series DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Website

iotdb.apache.org

clickhouse.com

cloud.google.com/datastore

firebase.google.com/products/firestore

github.com/spotify/heroic

Technical documentation

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

clickhouse.com/docs

cloud.google.com/datastore/docs

firebase.google.com/docs/firestore

spotify.github.io/heroic

Developer

Apache Software Foundation

Clickhouse Inc.

Google

Spotify

Initial release

2018

2016

2008

2017

2014

Current release

1.1.0, April 2023

v24.4.1.2088-stable, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

commercial

Open Source

Apache 2.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.

ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.

Implementation language

Java

C++

Java

Server operating systems

All OS with a Java VM (>= 1.8)

FreeBSD
Linux
macOS

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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 Elasticsearch

SQL

Support of SQL

SQL-like query language

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language (GQL)

APIs and other access methods

JDBC
Native API

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

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

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

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

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

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

Server-side scripts

Stored procedures

yes

using Google App Engine

yes, Firebase Rules & Cloud Functions

Triggers

yes

Callbacks using the Google Apps Engine

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

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

key based and custom

Sharding

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

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

Multi-source replication using Paxos

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

using Google Cloud Dataflow

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

yes

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.