DBMS > IRONdb vs. Microsoft Azure Cosmos DB vs. Quasardb vs. Trafodion

System Properties Comparison IRONdb vs. Microsoft Azure Cosmos DB vs. Quasardb vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Globally distributed, horizontally scalable, multi-model database service

Distributed, high-performance timeseries database

Transactional SQL-on-Hadoop DBMS

Primary database model

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Website

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

azure.microsoft.com/services/cosmos-db

quasar.ai

trafodion.apache.org

Technical documentation

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

learn.microsoft.com/azure/cosmos-db

doc.quasar.ai/master

trafodion.apache.org/documentation.html

Developer

Circonus LLC.

Microsoft

quasardb

Apache Software Foundation, originally developed by HP

Initial release

2017

2014

2009

2014

Current release

V0.10.20, January 2018

3.14.1, January 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Apache 2.0

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

C and C++

C++

C++, Java

Server operating systems

Linux

hosted

BSD
Linux
OS X
Windows

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

JSON types

yes

integer and binary

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

yes

with tags

yes

SQL

Support of SQL

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

SQL-like query language

yes

APIs and other access methods

HTTP API

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

HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

.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#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes, in Lua

JavaScript

Java Stored Procedures

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

Sharding

Implicit feature of the cloud service

Sharding

consistent hashing

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes

Implicit feature of the cloud service

Source-replica replication with selectable replication factor

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

with Hadoop integration

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

User concepts

Access control

Access rights can be defined down to the item level

Cryptographically strong user authentication and audit trail

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.