DBMS > Apache IoTDB vs. Ignite vs. Infobright vs. SAP HANA

System Properties Comparison Apache IoTDB vs. Ignite vs. Infobright 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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

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

Primary database model

Time Series DBMS

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

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	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

iotdb.apache.org

ignite.apache.org

ignitetech.com/softwarelibrary/infobrightdb

www.sap.com/products/hana.html

Technical documentation

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

apacheignite.readme.io/docs

help.sap.com/hana

Developer

Apache Software Foundation

Ignite Technologies Inc.; formerly InfoBright Inc.

SAP

Initial release

2018

2015

2005

2010

Current release

1.1.0, April 2023

Apache Ignite 2.6

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

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++, Java, .Net

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
OS X
Solaris
Windows

Linux
Windows

Appliance or cloud-service

Data scheme

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

SQL-like query language

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

JDBC
Native API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET
JDBC
ODBC

JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

yes (compute grid and cache interceptors can be used instead)

SQLScript, R

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

none

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

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes (compute grid and hadoop accelerator)

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

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.