DBMS > Apache IoTDB vs. GeoMesa vs. OrientDB vs. SAP HANA

System Properties Comparison Apache IoTDB vs. GeoMesa vs. OrientDB 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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Multi-model DBMS (Document, Graph, Key/Value)

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

Primary database model

Time Series DBMS

Spatial DBMS

Document store
Graph DBMS
Key-value store

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.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

iotdb.apache.org

www.geomesa.org

orientdb.org

www.sap.com/products/hana.html

Technical documentation

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

www.geomesa.org/documentation/stable/user/index.html

www.orientdb.com/docs/last/index.html

help.sap.com/hana

Developer

Apache Software Foundation

CCRi and others

OrientDB LTD; CallidusCloud; SAP

SAP

Initial release

2018

2014

2010

Current release

1.1.0, April 2023

4.0.5, February 2024

3.2.29, March 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

Open Source

Apache version 2

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

Scala

Java

Server operating systems

All OS with a Java VM (>= 1.8)

All OS with a Java JDK (>= JDK 6)

Appliance or cloud-service

Data scheme

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language, no joins

yes

APIs and other access methods

JDBC
Native API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

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

Server-side scripts

Stored procedures

yes

Java, Javascript

SQLScript, R

Triggers

yes

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

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

depending on storage layer

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

depending on storage layer

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users and roles; record level security configurable

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.