DBMS > Apache Phoenix vs. IRONdb vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage

System Properties Comparison Apache Phoenix vs. IRONdb vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

Globally distributed, horizontally scalable, multi-model database service

A Wide Column Store for rapid development using massive semi-structured datasets

Primary database model

Relational DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

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

Score	3.39
Rank	#94	Overall
	#47	Relational DBMS

Score	0.00
Rank	#335	Overall
	#31	Time Series DBMS

Score	32.97
Rank	#25	Overall
	#3	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	5.28
Rank	#70	Overall
	#5	Wide column stores

Website

phoenix.apache.org

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

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

Technical documentation

phoenix.apache.org

docs.circonus.com/irondb

docs.microsoft.com/azure/cosmos-db

Developer

Apache Software Foundation

Circonus LLC.

Microsoft

Initial release

2014

2017

2014

2012

Current release

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

V0.10.20, January 2018

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

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

Linux
Unix
Windows

Linux

hosted

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

JSON types

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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

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

SQL-like query language

APIs and other access methods

JDBC

HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

RESTful HTTP API

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes, in Lua

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

configurable replication factor, datacenter aware

yes

Implicit feature of the cloud service

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate consistency per node, eventual consistency across nodes

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

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

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

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

More information provided by the system vendor

Specific characteristics

IRONdb is a highly available, distributed Time Series Database. It can support dozens...
» more

Competitive advantages

Unmatched Scalability IRONdb is unique among TSDBs in that it does not use a consensus...
» more

Typical application scenarios

Real Systems Monitoring Monitor your systems infrastructure in real time across thousands...
» more

Key customers

IRONdb serves the needs of the world's largest Time Series Database customers. One...
» more

Market metrics

Only TSDB capable of scaling to billions of metrics. Only TSDB to scale to dozens...
» more

Licensing and pricing models

IRONdb is licensed under a subscription model based on the number of active metrics...
» more

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.