DBMS > atoti vs. Firebase Realtime Database vs. ITTIA vs. MySQL vs. WakandaDB

System Properties Comparison atoti vs. Firebase Realtime Database vs. ITTIA vs. MySQL vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

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

Edge Time Series DBMS with Real-Time Stream Processing

Widely used open source RDBMS

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Key/Value like access via memcached API

Object oriented DBMS

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

Score	0.45
Rank	#253	Overall
	#13	Object oriented DBMS

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	0.36
Rank	#272	Overall
	#22	Time Series DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

atoti.io

firebase.google.com/products/realtime-database

www.ittia.com

www.mysql.com

wakanda.github.io

Technical documentation

docs.atoti.io

firebase.google.com/docs/database

dev.mysql.com/doc

wakanda.github.io/doc

Developer

ActiveViam

Google

acquired by Google 2014

ITTIA L.L.C.

Oracle

since 2010, originally MySQL AB, then Sun

Wakanda SAS

Initial release

2012

2007

1995

2012

Current release

8.7

9.0.0, July 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

free versions available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPLv3, extended commercial license 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.

Implementation language

Java

C and C++

C++, JavaScript

Server operating systems

hosted

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

schema-free

Fixed schema

yes

Typing

predefined data types such as float or date

yes

Float/Blob/Integer/String/Unicode/Date/Time/Timestamp/Interval

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

Multidimensional Expressions (MDX)

yes

with proprietary extensions

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API
WebSocket

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

Supported programming languages

Java
JavaScript
Objective-C

C
C++
JavaScript (Node.js)
Python

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

JavaScript

Server-side scripts

Stored procedures

Python

limited functionality with using 'rules'

yes

proprietary syntax

yes

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding, horizontal partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

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

yes

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

yes, multi-version concurrency control (MVCC)

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

yes, based on authentication and database rules

Database file passwords

Users with fine-grained authorization concept

no user groups or roles

yes

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.