DBMS > Apache IoTDB vs. Axibase vs. Citus vs. MySQL

System Properties Comparison Apache IoTDB vs. Axibase vs. Citus vs. MySQL

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

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

Widely used open source RDBMS

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store

Document store
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	0.35
Rank	#282	Overall
	#25	Time Series DBMS

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

iotdb.apache.org

axibase.com/docs/atsd/finance

www.citusdata.com

www.mysql.com

Technical documentation

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

docs.citusdata.com

dev.mysql.com/doc

Developer

Apache Software Foundation

Axibase Corporation

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2018

2013

2010

1995

Current release

1.1.0, April 2023

15585

8.1, December 2018

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

AGPL, commercial license also available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

Server operating systems

All OS with a Java VM (>= 1.8)

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

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

specific XML type available, but no XML query functionality

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

standard, with numerous extensions

yes

with proprietary extensions

APIs and other access methods

JDBC
Native API

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

Go
Java
PHP
Python
R
Ruby

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

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

Source-replica replication

other methods possible by using 3rd party extensions

Multi-source replication
Source-replica 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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or 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.