DBMS > IRONdb vs. MySQL vs. SAP SQL Anywhere vs. Trino

System Properties Comparison IRONdb vs. MySQL vs. SAP SQL Anywhere vs. Trino

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Fast distributed SQL query engine for big data analytics. Forked from Presto and originally named PrestoSQL

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Key-value store
Spatial DBMS
Search engine
Time Series DBMS
Wide column store

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

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	3.50
Rank	#81	Overall
	#44	Relational DBMS

Score	5.28
Rank	#61	Overall
	#35	Relational DBMS

Website

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

www.mysql.com

www.sap.com/products/technology-platform/sql-anywhere.html

trino.io

Technical documentation

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

dev.mysql.com/doc

help.sap.com/docs/SAP_SQL_Anywhere

trino.io/broadcast
trino.io/docs/current

Developer

Circonus LLC.

Oracle

since 2010, originally MySQL AB, then Sun

SAP

formerly Sybase

Trino Software Foundation

Initial release

2017

1995

1992

2012

2020 rebranded from PrestoSQL

Current release

V0.10.20, January 2018

9.0.0, July 2024

17, July 2015

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

Apache Version 2.0

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.

Implementation language

C and C++

Java

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
macOS

for devlopment

Data scheme

schema-free

yes

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

depending on connected data-source

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

ADO.NET
HTTP API
JDBC
ODBC

JDBC
RESTful HTTP API
Trino CLI

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++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
Python
R
Ruby

Server-side scripts

Stored procedures

yes, in Lua

yes

proprietary syntax

yes, in C/C++, Java, .Net or Perl

yes, depending on connected data-source

Triggers

yes

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

depending on connected data-source

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

Multi-source replication
Source-replica replication

Source-replica replication

Database mirroring

depending on connected data-source

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

depending on connected data-source

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

depending on connected data-source

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

depending on connected data-source

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

SQL standard access control

More information provided by the system vendor

News

23 is a go, keeping pace with Java
17 September 2024

65: Performance boosts
12 September 2024

64: Control with Open Policy Agent OPA
22 August 2024

63: Querying with JS
1 August 2024

62: A lakehouse that simply works at Prezi
11 July 2024

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.