DBMS > Apache IoTDB vs. Hazelcast vs. HEAVY.AI vs. SAP HANA

System Properties Comparison Apache IoTDB vs. Hazelcast vs. HEAVY.AI 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

A widely adopted in-memory data grid

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

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

Primary database model

Time Series DBMS

Key-value store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS

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	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

iotdb.apache.org

hazelcast.com

github.com/heavyai/heavydb
www.heavy.ai

www.sap.com/products/hana.html

Technical documentation

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

hazelcast.org/imdg/docs

docs.heavy.ai

help.sap.com/hana

Developer

Apache Software Foundation

Hazelcast

HEAVY.AI, Inc.

SAP

Initial release

2018

2008

2016

2010

Current release

1.1.0, April 2023

5.3.6, November 2023

5.10, January 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache Version 2; enterprise edition 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

C++ and CUDA

Server operating systems

All OS with a Java VM (>= 1.8)

All OS with a Java VM

Linux

Appliance or cloud-service

Data scheme

yes

schema-free

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

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

JDBC
Native API

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC
Thrift
Vega

JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

All languages supporting JDBC/ODBC/Thrift
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

SQLScript, R

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

Round robin

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

yes

Replicated Map

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

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

Role-based access control

fine grained access rights according to SQL-standard

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.