DBMS > Apache IoTDB vs. Citus vs. CockroachDB vs. SAP HANA

System Properties Comparison Apache IoTDB vs. Citus vs. CockroachDB vs. SAP HANA

Please select another system to include it in the comparison.

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

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

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Time Series DBMS

Relational DBMS

Secondary database models

Document store

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

iotdb.apache.org

www.citusdata.com

www.cockroachlabs.com

www.sap.com/products/hana.html

Technical documentation

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

docs.citusdata.com

www.cockroachlabs.com/docs

help.sap.com/hana

Developer

Apache Software Foundation

Cockroach Labs

SAP

Initial release

2018

2010

2015

2010

Current release

1.1.0, April 2023

8.1, December 2018

24.1.0, May 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

AGPL, commercial license also available

Open Source

Apache 2.0, commercial license available

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

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)

Linux

Linux
macOS
Windows

Appliance or cloud-service

Data scheme

yes

dynamic schema

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

specific XML type available, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

standard, with numerous extensions

yes, wire compatible with PostgreSQL

yes

APIs and other access methods

JDBC
Native API

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

JDBC

JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

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

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

Server-side scripts

Stored procedures

yes

user defined functions

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

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

yes

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

other methods possible by using 3rd party extensions

Multi-source replication using RAFT

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

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

Role-based access control

yes

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.