DBMS > Apache IoTDB vs. Apache Phoenix vs. MySQL vs. Oracle Coherence

System Properties Comparison Apache IoTDB vs. Apache Phoenix vs. MySQL vs. Oracle Coherence

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

A scale-out RDBMS with evolutionary schema built on Apache HBase

Widely used open source RDBMS

Oracles in-memory data grid solution

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Key-value store

Secondary database models

Document store
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	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.92
Rank	#130	Overall
	#22	Key-value stores

Website

iotdb.apache.org

phoenix.apache.org

www.mysql.com

www.oracle.com/java/coherence

Technical documentation

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

phoenix.apache.org

dev.mysql.com/doc

docs.oracle.com/en/middleware/standalone/coherence

Developer

Apache Software Foundation

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

Initial release

2018

2014

1995

2007

Current release

1.1.0, April 2023

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

8.4.0, April 2024

14.1, August 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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

Java

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
Unix
Windows

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

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

APIs and other access methods

JDBC
Native API

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

JCache
JPA
RESTful HTTP API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

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

.Net
C++
Java

Server-side scripts

Stored procedures

yes

user defined functions

yes

proprietary syntax

Triggers

yes

Live Events

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

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

yes, with selectable consistency level

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency
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

configurable

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

optionally

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Users with fine-grained authorization concept

no user groups or roles

authentification to access the cache via certificates or http basic authentication

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.