DBMS > Apache IoTDB vs. Cubrid vs. Heroic vs. Snowflake vs. TerminusDB

System Properties Comparison Apache IoTDB vs. Cubrid vs. Heroic vs. Snowflake vs. TerminusDB

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

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

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

Cloud-based data warehousing service for structured and semi-structured data

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Document store
RDF store

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	1.04
Rank	#187	Overall
	#87	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

iotdb.apache.org

cubrid.com (korean)
cubrid.org (english)

github.com/spotify/heroic

www.snowflake.com

terminusdb.com

Technical documentation

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

cubrid.org/manuals

spotify.github.io/heroic

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

Developer

Apache Software Foundation

CUBRID Corporation, CUBRID Foundation

Spotify

Snowflake Computing Inc.

DataChemist Ltd.

Initial release

2018

2008

2014

2018

Current release

1.1.0, April 2023

11.0, January 2021

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

Open Source

Apache 2.0

commercial

Open Source

GPL V3

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

C, C++, Java

Java

Prolog, Rust

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
Windows

hosted

Linux

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

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

Secondary indexes

yes

via Elasticsearch

SQL

Support of SQL

SQL-like query language

yes

SQL-like query language (WOQL)

APIs and other access methods

JDBC
Native API

ADO.NET
JDBC
ODBC
OLE DB

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

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C
C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

JavaScript
Python

Server-side scripts

Stored procedures

yes

Java Stored Procedures

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

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

none

Sharding

yes

Graph Partitioning

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

Source-replica replication

yes

Journaling Streams

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

Users with fine-grained authorization concept, user roles and pluggable authentication

Role-based access control

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.