DBMS > Firebase Realtime Database vs. GeoMesa vs. mSQL vs. OpenQM vs. Warp 10

System Properties Comparison Firebase Realtime Database vs. GeoMesa vs. mSQL vs. OpenQM vs. Warp 10

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.

mSQL (Mini SQL) is a simple and lightweight RDBMS

QpenQM is a high-performance, self-tuning, multi-value DBMS

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

firebase.google.com/products/realtime-database

www.geomesa.org

hughestech.com.au/products/msql

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.warp10.io

Technical documentation

firebase.google.com/docs/database

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

www.warp10.io/content/02_Getting_started

Developer

Google

acquired by Google 2014

CCRi and others

Hughes Technologies

Rocket Software, originally Martin Phillips

SenX

Initial release

2012

2014

1994

1993

2015

Current release

5.0.0, May 2024

4.4, October 2021

3.4-12

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

free licenses can be provided

Open Source

GPLv2, extended commercial license available

Open Source

Apache License 2.0

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

Java

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

with some exceptions

schema-free

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

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

Java
JavaScript
Objective-C

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

WarpScript

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

yes

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

yes

selectable replication factor

based on HBase

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

none

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

Transaction concepts

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

yes

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

yes

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Realtime vs Cloud Firestore: Which Firebase Database to go?
8 March 2024, Appinventiv

Atos cybersecurity blog: Misconfigured Firebase: A real-time cyber threat
18 January 2024, Atos

Google launches Firebase Genkit, a new open source framework for building AI-powered apps
14 May 2024, TechCrunch

Don't be like these 900+ websites and expose millions of passwords via Firebase
18 March 2024, The Register

Google Firebase may have exposed 125M records from misconfigurations
19 March 2024, SC Media

provided by Google News

Higher Education PS rules out ghost students before PAC
29 November 2018, diggers.news

provided by Google News

Time Series Databases Software market latest trends, CAGR, and forecast till 2026 | eSherpa Market Reports
13 April 2020, openPR

provided by Google News

Share this page