DBMS > Apache IoTDB vs. Microsoft Azure Synapse Analytics vs. SAP HANA vs. SingleStore

System Properties Comparison Apache IoTDB vs. Microsoft Azure Synapse Analytics vs. SAP HANA vs. SingleStore

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

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

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

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Primary database model

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	1.31
Rank	#159	Overall
	#14	Time Series DBMS

Score	18.98
Rank	#31	Overall
	#19	Relational DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Website

iotdb.apache.org

azure.microsoft.com/services/synapse-analytics

www.sap.com/products/hana.html

www.singlestore.com

Technical documentation

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

docs.microsoft.com/azure/synapse-analytics

help.sap.com/hana

docs.singlestore.com

Developer

Apache Software Foundation

Microsoft

SAP

SingleStore Inc.

Initial release

2018

2016

2010

2013

Current release

1.1.0, April 2023

2.0 SPS07 (April 4, 2023), April 2023

8.5, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free developer edition available

Cloud-based only

Only available as a cloud service

yes

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

C++, Go

Server operating systems

All OS with a Java VM (>= 1.8)

hosted

Appliance or cloud-service

Linux

64 bit version required

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

but no triggers and foreign keys

APIs and other access methods

JDBC
Native API

ADO.NET
JDBC
ODBC

JDBC
ODBC

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C#
Java
PHP

Bash
C
C#
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Transact SQL

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding, horizontal partitioning

yes

Sharding

hash partitioning

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

Source-replica replication

stores two copies of each physical data partition on two separate nodes

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Foreign keys

Referential integrity

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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 control via users, groups and roles

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.