DBMS > Apache IoTDB vs. Drizzle vs. SAP HANA vs. Tibero

System Properties Comparison Apache IoTDB vs. Drizzle vs. SAP HANA vs. Tibero

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

A secure RDBMS, designed for easy portability from Oracle

Primary database model

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

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

iotdb.apache.org

www.sap.com/products/hana.html

us.tmaxsoft.com/products/tibero

Technical documentation

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

help.sap.com/hana

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Apache Software Foundation

Drizzle project, originally started by Brian Aker

SAP

TmaxSoft

Initial release

2018

2008

2010

2003

Current release

1.1.0, April 2023

7.2.4, September 2012

2.0 SPS07 (April 4, 2023), April 2023

6, April 2015

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GNU GPL

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

C and Assembler

Server operating systems

All OS with a Java VM (>= 1.8)

FreeBSD
Linux
OS X

Appliance or cloud-service

AIX
HP-UX
Linux
Solaris
Windows

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

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
Native API

JDBC

JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C
C++
Java
PHP

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

yes

SQLScript, R

Persistent Stored Procedure (PSM)

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

yes

horizontal partitioning

by range, hash, list or composite

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

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

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

planned for next version

User concepts

Access control

yes

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.