DBMS > IRONdb vs. Snowflake vs. TimescaleDB vs. ToroDB

System Properties Comparison IRONdb vs. Snowflake vs. TimescaleDB vs. ToroDB

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.

ToroDB seems to be discontinued. 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

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

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

Relational DBMS

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

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

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

www.snowflake.com

www.timescale.com

github.com/torodb/server

Technical documentation

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

docs.snowflake.net/manuals/index.html

docs.timescale.com

Developer

Circonus LLC.

Snowflake Computing Inc.

Timescale

8Kdata

Initial release

2017

2014

2017

2016

Current release

V0.10.20, January 2018

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

AGPL-V3

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++

Java

Server operating systems

Linux

hosted

Linux
OS X
Windows

All OS with a Java 7 VM

Data scheme

schema-free

yes

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

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

yes

string, integer, double, boolean, date, object_id

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

SQL

Support of SQL

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

yes

full PostgreSQL SQL syntax

APIs and other access methods

HTTP API

CLI Client
JDBC
ODBC

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

Supported programming languages

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

JavaScript (Node.js)
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes, in Lua

user defined functions

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

yes

yes, across time and space (hash partitioning) attributes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes

Source-replica replication with hot standby and reads on replicas

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Eventual Consistency
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

In-memory capabilities

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

User concepts

Access control

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

fine grained access rights according to SQL-standard

Access rights for users and roles

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.