DBMS > IRONdb vs. MySQL vs. SpatiaLite vs. Teradata

System Properties Comparison IRONdb vs. MySQL vs. SpatiaLite vs. Teradata

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 SQLite

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Website

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

www.mysql.com

www.gaia-gis.it/fossil/libspatialite/index

www.teradata.com

Technical documentation

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

dev.mysql.com/doc

www.gaia-gis.it/gaia-sins/spatialite_topics.html

docs.teradata.com

Developer

Circonus LLC.

Oracle

since 2010, originally MySQL AB, then Sun

Alessandro Furieri

Teradata

Initial release

2017

1995

2008

1984

Current release

V0.10.20, January 2018

8.4.0, April 2024

5.0.0, August 2020

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

commercial

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

C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

server-less

hosted
Linux

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

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

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

yes

with proprietary extensions

yes

SQL 2016 + extensions

APIs and other access methods

HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

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++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

yes, in Lua

yes

proprietary syntax

yes

UDFs, stored procedures, table functions in parallel

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

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

Multi-source replication
Source-replica replication

none

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

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

fine grained access rights according to SQL-standard

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.