DBMS > Apache IoTDB vs. Apache Phoenix vs. Citus vs. Oracle vs. Yanza

System Properties Comparison Apache IoTDB vs. Apache Phoenix vs. Citus vs. Oracle vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it 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

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

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

Widely used RDBMS

Time Series DBMS for IoT Applications

Primary database model

Time Series DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Document store

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Website

iotdb.apache.org

phoenix.apache.org

www.citusdata.com

www.oracle.com/database

yanza.com

Technical documentation

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

phoenix.apache.org

docs.citusdata.com

docs.oracle.com/en/database

Developer

Apache Software Foundation

Oracle

Yanza

Initial release

2018

2014

2010

1980

2015

Current release

1.1.0, April 2023

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

8.1, December 2018

23c, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

Open Source

AGPL, commercial license also available

commercial

restricted free version is available

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

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
Unix
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

Schemaless in JSON and XML columns

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

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

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

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

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

user defined functions

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

PL/SQL

also stored procedures in Java possible

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

Sharding, horizontal partitioning

none

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

Source-replica replication

other methods possible by using 3rd party extensions

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Hadoop integration

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

yes

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

fine grained access rights according to SQL-standard

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.