DBMS > Apache IoTDB vs. Percona Server for MySQL vs. SAP HANA vs. Splunk

System Properties Comparison Apache IoTDB vs. Percona Server for MySQL vs. SAP HANA vs. Splunk

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

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

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

Analytics Platform for Big Data

Primary database model

Time Series DBMS

Relational DBMS

Search engine

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	#159	Overall
	#14	Time Series DBMS

Score	2.06
Rank	#118	Overall
	#57	Relational DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Score	93.02
Rank	#13	Overall
	#2	Search engines

Website

iotdb.apache.org

www.percona.com/software/mysql-database/percona-server

www.sap.com/products/hana.html

www.splunk.com

Technical documentation

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

www.percona.com/downloads/Percona-Server-LATEST

help.sap.com/hana

docs.splunk.com/Documentation/Splunk

Developer

Apache Software Foundation

Percona

SAP

Splunk Inc.

Initial release

2018

2008

2010

2003

Current release

1.1.0, April 2023

8.0.36-28, 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPL version 2

commercial

Limited free edition and free developer edition available

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

Server operating systems

All OS with a Java VM (>= 1.8)

Linux

Appliance or cloud-service

Linux
OS X
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

Splunk Search Processing Language for search commands

APIs and other access methods

JDBC
Native API

ADO.NET
JDBC
ODBC

JDBC
ODBC

HTTP REST

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

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

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

yes

Sharding

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
XtraDB Cluster

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

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

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

Users with fine-grained authorization concept

no user groups or roles

yes

Access rights for users 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.