DBMS > IRONdb vs. Quasardb vs. SiriDB vs. Snowflake vs. Trafodion

System Properties Comparison IRONdb vs. Quasardb vs. SiriDB vs. Snowflake vs. Trafodion

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

Distributed, high-performance timeseries database

Open Source Time Series DBMS

Cloud-based data warehousing service for structured and semi-structured data

Transactional SQL-on-Hadoop DBMS

Primary database model

Time Series DBMS

Relational DBMS

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

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

Technical documentation

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

doc.quasar.ai/master

docs.siridb.com

docs.snowflake.net/manuals/index.html

trafodion.apache.org/documentation.html

Developer

Circonus LLC.

quasardb

Cesbit

Snowflake Computing Inc.

Apache Software Foundation, originally developed by HP

Initial release

2017

2009

2017

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

MIT License

commercial

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

BSD
Linux
OS X
Windows

Linux

hosted

Linux

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

integer and binary

yes

Numeric data

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

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

CLI Client
JDBC
ODBC

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

JavaScript (Node.js)
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes, in Lua

user defined functions

Java Stored Procedures

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

Sharding

consistent hashing

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

Source-replica replication with selectable replication factor

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

yes

User concepts

Access control

Cryptographically strong user authentication and audit trail

simple rights management via user accounts

Users with fine-grained authorization concept, user roles and pluggable authentication

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.