DBMS > Altibase vs. IRONdb vs. MySQL vs. PostGIS vs. XTDB

System Properties Comparison Altibase vs. IRONdb vs. MySQL vs. PostGIS vs. XTDB

Editorial information provided by DB-Engines

Name

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

Description

An enterprise grade, high-performance RDBMS

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

Widely used open source RDBMS

Spatial extension of PostgreSQL

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Document store

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	1.02
Rank	#189	Overall
	#88	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

altibase.com

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

www.mysql.com

postgis.net

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

github.com/ALTIBASE/Documents/tree/master/Manuals

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

dev.mysql.com/doc

postgis.net/documentation

www.xtdb.com/docs

Developer

Altibase

Circonus LLC.

Oracle

since 2010, originally MySQL AB, then Sun

Juxt Ltd.

Initial release

1999

2017

1995

2005

2019

Current release

v7.3, 2023, August 2023

V0.10.20, January 2018

8.4.0, April 2024

3.4.2, February 2024

1.19, September 2021

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.0

Open Source

MIT License

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

C and C++

Clojure

Server operating systems

AIX
HP-UX
Linux

Linux

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

yes, extensible-data-notation format

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

ANSI SQL-92

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

yes

with proprietary extensions

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC
Proprietary protocol

HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
JDBC

Supported programming languages

C
C++
Java

.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

Clojure
Java

Server-side scripts

Stored procedures

stored procedures and stored functions

yes, in Lua

yes

proprietary syntax

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

configurable replication factor, datacenter aware

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Users with fine-grained authorization concept

no user groups or roles

yes

based on PostgreSQL

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.