DBMS > IRONdb vs. MySQL vs. Transbase vs. UniData,UniVerse vs. VoltDB

System Properties Comparison IRONdb vs. MySQL vs. Transbase vs. UniData,UniVerse vs. VoltDB

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

A resource-optimized, high-performance, universally applicable RDBMS

MultiValue database and application server with SQL mapping layer and meta database capabilities

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Multivalue DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Score	2.85
Rank	#98	Overall
	#1	Multivalue DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

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

www.mysql.com

www.transaction.de/en/products/transbase.html

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-unidata

www.voltdb.com

Technical documentation

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

dev.mysql.com/doc

www.transaction.de/en/products/transbase/features.html

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

docs.voltdb.com

Developer

Circonus LLC.

Oracle

since 2010, originally MySQL AB, then Sun

Transaction Software GmbH

Rocket Software

VoltDB Inc.

Initial release

2017

1995

1987

1985

2010

Current release

V0.10.20, January 2018

8.4.0, April 2024

Transbase 8.3, 2022

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

free development license

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

Linux
OS X

for development

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

optional

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

SQL

Support of SQL

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

yes

with proprietary extensions

yes

only a subset of SQL 99

APIs and other access methods

HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Java API
JDBC
RESTful HTTP/JSON 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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

.Net
Basic

U2 Basic
C
Java

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes, in Lua

yes

proprietary syntax

yes

Java

Triggers

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

Multi-source replication
Source-replica replication

Source-replica replication

Multi-source replication
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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

not for MyISAM storage engine

yes

ACID

configurable

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

fine grained access rights according to SQL-standard

Access rights according to SQL-standard and operating system based

Users and roles with access to stored procedures

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.