DBMS > Apache IoTDB vs. BigchainDB vs. Citus vs. Google BigQuery vs. Heroic

System Properties Comparison Apache IoTDB vs. BigchainDB vs. Citus vs. Google BigQuery 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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Large scale data warehouse service with append-only tables

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

Primary database model

Secondary database models

Document store

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Website

iotdb.apache.org

www.bigchaindb.com

www.citusdata.com

cloud.google.com/bigquery

github.com/spotify/heroic

Technical documentation

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

bigchaindb.readthedocs.io/en/latest

docs.citusdata.com

cloud.google.com/bigquery/docs

spotify.github.io/heroic

Developer

Apache Software Foundation

Google

Spotify

Initial release

2018

2016

2010

2014

Current release

1.1.0, April 2023

8.1, December 2018

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

AGPL v3

Open Source

AGPL, commercial license also available

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.

Implementation language

Java

Python

Java

Server operating systems

All OS with a Java VM (>= 1.8)

Linux

hosted

Data scheme

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.

yes

specific XML type available, but no XML query functionality

Secondary indexes

yes

via Elasticsearch

SQL

Support of SQL

SQL-like query language

yes

standard, with numerous extensions

yes

APIs and other access methods

JDBC
Native API

CLI Client
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP/JSON API

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

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

none

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

selectable replication factor

Source-replica replication

other methods possible by using 3rd party extensions

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

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

fine grained access rights according to SQL-standard

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.