DBMS > Firebase Realtime Database vs. GeoMesa vs. Heroic vs. Postgres-XL vs. Warp 10

System Properties Comparison Firebase Realtime Database vs. GeoMesa vs. Heroic vs. Postgres-XL 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.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Primary database model

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	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

firebase.google.com/products/realtime-database

www.geomesa.org

github.com/spotify/heroic

www.postgres-xl.org

www.warp10.io

Technical documentation

firebase.google.com/docs/database

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

spotify.github.io/heroic

www.postgres-xl.org/documentation

www.warp10.io/content/02_Getting_started

Developer

Google

acquired by Google 2014

CCRi and others

Spotify

SenX

Initial release

2012

2014

since 2012, originally named StormDB

2015

Current release

4.0.5, February 2024

10 R1, October 2018

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

Mozilla public license

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

Linux
macOS

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

yes

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

XML type, but no XML query functionality

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

distributed, parallel query execution

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API
Jupyter
WebSocket

Supported programming languages

Java
JavaScript
Objective-C

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

yes

WarpScript

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

MVCC

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

fine grained access rights according to SQL-standard

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

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

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

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

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Time Series Intelligence Software Market Business Insights, Key Trend Analysis | Google, SAP, Azure Time Series ...
24 April 2024, Amoré

provided by Google News

Share this page