DBMS > Firebase Realtime Database vs. GeoMesa vs. Microsoft Azure Cosmos DB vs. WakandaDB

System Properties Comparison Firebase Realtime Database vs. GeoMesa vs. Microsoft Azure Cosmos DB vs. WakandaDB

Please select another system to include it in the comparison.

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.

Globally distributed, horizontally scalable, multi-model database service

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

Document store
Graph DBMS
Key-value store
Wide column store

Object oriented DBMS

Secondary database models

Spatial DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

firebase.google.com/products/realtime-database

www.geomesa.org

azure.microsoft.com/services/cosmos-db

wakanda.github.io

Technical documentation

firebase.google.com/docs/database

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

learn.microsoft.com/azure/cosmos-db

wakanda.github.io/doc

Developer

Google

acquired by Google 2014

CCRi and others

Microsoft

Wakanda SAS

Initial release

2012

2014

2012

Current release

5.0.0, May 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

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

Server operating systems

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

RESTful HTTP API

Supported programming languages

Java
JavaScript
Objective-C

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

JavaScript

Server-side scripts

Stored procedures

limited functionality with using 'rules'

JavaScript

yes

Triggers

Callbacks are triggered when data changes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Implicit feature of the cloud service

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

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

User concepts

Access control

yes, based on authentication and database rules

yes

depending on the DBMS used for storage

Access rights can be defined down to the item level

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.