DBMS > Firebase Realtime Database vs. GeoMesa vs. MySQL vs. Transbase vs. WakandaDB

System Properties Comparison Firebase Realtime Database vs. GeoMesa vs. MySQL vs. Transbase vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Widely used open source RDBMS

A resource-optimized, high-performance, universally applicable 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

Spatial DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Object oriented DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.05
Rank	#355	Overall
	#150	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

firebase.google.com/products/realtime-database

www.geomesa.org

www.mysql.com

www.transaction.de/en/products/transbase.html

wakanda.github.io

Technical documentation

firebase.google.com/docs/database

www.geomesa.org/documentation/stable/user/index.html

dev.mysql.com/doc

www.transaction.de/en/products/transbase/features.html

wakanda.github.io/doc

Developer

Google

acquired by Google 2014

CCRi and others

Oracle

since 2010, originally MySQL AB, then Sun

Transaction Software GmbH

Wakanda SAS

Initial release

2012

2014

1995

1987

2012

Current release

5.0.1, July 2024

9.0.0, July 2024

Transbase 8.3, 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

free development license

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

Scala

C and C++

C++, JavaScript

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS
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

yes

with proprietary extensions

yes

APIs and other access methods

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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

JavaScript

Server-side scripts

Stored procedures

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

depending on storage layer

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica 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

if the client is offline
Immediate Consistency

if the client is online

depending on storage layer

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

yes

ACID

not for MyISAM storage engine

yes

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.

depending on storage layer

yes

User concepts

Access control

yes, based on authentication and database rules

yes

depending on the DBMS used for storage

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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.