DBMS > FatDB vs. Firebase Realtime Database vs. MySQL vs. WakandaDB

System Properties Comparison FatDB vs. Firebase Realtime Database vs. MySQL vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

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

Document store
Key-value store

Document store

Relational DBMS

Key/Value like access via memcached API

Object oriented DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

firebase.google.com/products/realtime-database

www.mysql.com

wakanda.github.io

Technical documentation

firebase.google.com/docs/database

dev.mysql.com/doc

wakanda.github.io/doc

Developer

FatCloud

Google

acquired by Google 2014

Oracle

since 2010, originally MySQL AB, then Sun

Wakanda SAS

Initial release

2012

1995

2012

Current release

8.3.0, January 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

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.

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

Server operating systems

Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

Via inetgration in SQL Server

yes

with proprietary extensions

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

Supported programming languages

Java
JavaScript
Objective-C

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

yes

via applications

limited functionality with using 'rules'

yes

proprietary syntax

yes

Triggers

yes

via applications

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

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

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

Can implement custom security layer via applications

yes, based on authentication and database rules

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.