DBMS > Apache IoTDB vs. ClickHouse vs. etcd vs. Google Cloud Firestore vs. Riak TS

System Properties Comparison Apache IoTDB vs. ClickHouse vs. etcd vs. Google Cloud Firestore vs. Riak TS

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.

A distributed reliable key-value store

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.

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

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	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

iotdb.apache.org

clickhouse.com

etcd.io
github.com/etcd-io/etcd

firebase.google.com/products/firestore

Technical documentation

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

clickhouse.com/docs

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

firebase.google.com/docs/firestore

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

Developer

Apache Software Foundation

Clickhouse Inc.

Google

Open Source, formerly Basho Technologies

Initial release

2018

2016

2017

2015

Current release

1.1.0, April 2023

v24.4.1.2088-stable, May 2024

3.4, August 2019

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

Apache Version 2.0

commercial

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.

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++

Erlang

Server operating systems

All OS with a Java VM (>= 1.8)

FreeBSD
Linux
macOS

FreeBSD
Linux
Windows

experimental

hosted

Linux
OS X

Data scheme

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

Close to ANSI SQL (SQL/JSON + extensions)

yes, limited

APIs and other access methods

JDBC
Native API

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

gRPC
JSON over HTTP

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

HTTP API
Native Erlang Interface

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
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
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

yes, Firebase Rules & Cloud Functions

Erlang

Triggers

yes

yes, watching key changes

yes, with Cloud Functions

yes

pre-commit hooks and post-commit hooks

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.

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Multi-source replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Using Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

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