DBMS > IRONdb vs. Microsoft SQL Server vs. Postgres-XL vs. Riak KV vs. TempoIQ

System Properties Comparison IRONdb vs. Microsoft SQL Server vs. Postgres-XL vs. Riak KV vs. TempoIQ

Editorial information provided by DB-Engines

Name

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

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

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

Microsofts flagship relational DBMS

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Distributed, fault tolerant key-value store

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Time Series DBMS

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

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

www.microsoft.com/en-us/sql-server

www.postgres-xl.org

tempoiq.com (offline)

Technical documentation

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

learn.microsoft.com/en-US/sql/sql-server

www.postgres-xl.org/documentation

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Circonus LLC.

Microsoft

OpenSource, formerly Basho Technologies

TempoIQ

Initial release

2017

1989

2014

since 2012, originally named StormDB

2009

2012

Current release

V0.10.20, January 2018

SQL Server 2022, November 2022

10 R1, October 2018

3.2.0, December 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Mozilla public license

Open Source

Apache version 2, commercial enterprise edition

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

C and C++

C++

Erlang

Server operating systems

Linux

Linux
Windows

Linux
macOS

Linux
OS X

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

XML type, but no XML query functionality

Secondary indexes

yes

restricted

SQL

Support of SQL

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

yes

distributed, parallel query execution

APIs and other access methods

HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

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

HTTP API
Native Erlang Interface

HTTP API

Supported programming languages

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes, in Lua

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

tables can be distributed across several files (horizontal partitioning); sharding through federation

horizontal partitioning

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes, but depending on the SQL-Server Edition

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

ACID

MVCC

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

fine grained access rights according to SQL-standard

yes, using Riak Security

simple authentication-based access control

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.