DBMS > Apache IoTDB vs. GridGain vs. SAP HANA vs. VictoriaMetrics

System Properties Comparison Apache IoTDB vs. GridGain vs. SAP HANA vs. VictoriaMetrics

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

GridGain is an in-memory computing platform, built on Apache Ignite

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

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Time Series DBMS

Key-value store
Relational DBMS

Relational DBMS

Time Series 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	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	1.23
Rank	#172	Overall
	#15	Time Series DBMS

Website

iotdb.apache.org

www.gridgain.com

www.sap.com/products/hana.html

victoriametrics.com

Technical documentation

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

www.gridgain.com/docs/index.html

help.sap.com/hana

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Apache Software Foundation

GridGain Systems, Inc.

SAP

VictoriaMetrics

Initial release

2018

2007

2010

2018

Current release

1.1.0, April 2023

GridGain 8.5.1

2.0 SPS07 (April 4, 2023), April 2023

v1.91, May 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Apache Version 2.0

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

Java, C++, .Net

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
OS X
Solaris
Windows

Appliance or cloud-service

FreeBSD
Linux
macOS
OpenBSD

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

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

JDBC
ODBC

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

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

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)

yes

Synchronous replication

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

Eventual 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

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.