DBMS > IRONdb vs. MySQL vs. PostGIS vs. Riak KV

System Properties Comparison IRONdb vs. MySQL vs. PostGIS vs. Riak KV

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.

Description

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

Widely used open source RDBMS

Spatial extension of PostgreSQL

Distributed, fault tolerant key-value store

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Key-value store

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

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

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

Website

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

www.mysql.com

postgis.net

Technical documentation

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

dev.mysql.com/doc

postgis.net/documentation

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

Developer

Circonus LLC.

Oracle

since 2010, originally MySQL AB, then Sun

OpenSource, formerly Basho Technologies

Initial release

2017

1995

2005

2009

Current release

V0.10.20, January 2018

8.3.0, January 2024

3.4.2, February 2024

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.0

Open Source

Apache version 2, commercial enterprise edition

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Erlang

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

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

Secondary indexes

yes

restricted

SQL

Support of SQL

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

yes

with proprietary extensions

yes

APIs and other access methods

HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Native Erlang Interface

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
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

Server-side scripts

Stored procedures

yes, in Lua

yes

proprietary syntax

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

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

not for MyISAM storage engine

yes

links between data sets can be stored

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

yes

based on PostgreSQL

yes, using Riak Security

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.