DBMS > EXASOL vs. Firebase Realtime Database vs. IRONdb vs. MySQL

System Properties Comparison EXASOL vs. Firebase Realtime Database vs. IRONdb vs. MySQL

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

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

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

www.exasol.com

firebase.google.com/products/realtime-database

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

www.mysql.com

Technical documentation

www.exasol.com/resources

firebase.google.com/docs/database

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

dev.mysql.com/doc

Developer

Exasol

Google

acquired by Google 2014

Circonus LLC.

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2000

2012

2017

1995

Current release

V0.10.20, January 2018

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

yes

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

Server operating systems

hosted

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

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

SQL

Support of SQL

yes

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

yes

with proprietary extensions

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

Android
iOS
JavaScript API
RESTful HTTP API

HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Java
Lua
Python
R

Java
JavaScript
Objective-C

.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

Server-side scripts

Stored procedures

user defined functions

limited functionality with using 'rules'

yes, in Lua

yes

proprietary syntax

Triggers

yes

Callbacks are triggered when data changes

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

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

yes

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Access rights for users, groups and roles according to SQL-standard

yes, based on authentication and database rules

Users with fine-grained authorization concept

no user groups or roles

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.