DBMS > Apache Phoenix vs. Datomic vs. Hypertable vs. IRONdb vs. RocksDB

System Properties Comparison Apache Phoenix vs. Datomic vs. Hypertable vs. IRONdb vs. RocksDB

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

An open source BigTable implementation based on distributed file systems such as Hadoop

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	2.02
Rank	#130	Overall
	#63	Relational DBMS

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Website

phoenix.apache.org

www.datomic.com

www.circonus.com/solutions/time-series-database/

rocksdb.org

Technical documentation

phoenix.apache.org

docs.datomic.com

docs.circonus.com/irondb/category/getting-started

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Cognitect

Hypertable Inc.

Circonus LLC.

Facebook, Inc.

Initial release

2014

2012

2009

2017

2013

Current release

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

1.0.6735, June 2023

0.9.8.11, March 2016

V0.10.20, January 2018

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

limited edition free

Open Source

GNU version 3. Commercial license available

commercial

Open Source

BSD

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.

Implementation language

Java

Java, Clojure

C++

C and C++

C++

Server operating systems

Linux
Unix
Windows

All OS with a Java VM

Linux
OS X
Windows

an inofficial Windows port is available

Linux

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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.

Secondary indexes

yes

restricted

only exact value or prefix value scans

SQL

Support of SQL

yes

SQL-like query language (Circonus Analytics Query Language: CAQL)

APIs and other access methods

JDBC

RESTful HTTP API

C++ API
Thrift

HTTP API

C++ API
Java API

Supported programming languages

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

Clojure
Java

C++
Java
Perl
PHP
Python
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Transaction Functions

yes, in Lua

Triggers

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

Automatic, metric affinity per node

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

But extensive use of caching in the application peers

selectable replication factor on file system level

configurable replication factor, datacenter aware

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Foreign keys

Referential integrity

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

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

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.