DBMS > Firebase Realtime Database vs. GeoMesa vs. GigaSpaces vs. RocksDB

System Properties Comparison Firebase Realtime Database vs. GeoMesa vs. GigaSpaces vs. RocksDB

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.

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store

Spatial DBMS

Document store
Object oriented DBMS

Values are user defined objects

Key-value store

Secondary database models

Graph DBMS
Search engine

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.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

firebase.google.com/products/realtime-database

www.geomesa.org

www.gigaspaces.com

rocksdb.org

Technical documentation

firebase.google.com/docs/database

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

docs.gigaspaces.com/latest/landing.html

github.com/facebook/rocksdb/wiki

Developer

Google

acquired by Google 2014

CCRi and others

Gigaspaces Technologies

Facebook, Inc.

Initial release

2012

2014

2000

2013

Current release

4.0.5, February 2024

15.5, September 2020

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache Version 2; Commercial licenses available

Open Source

BSD

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, C++, .Net

C++

Server operating systems

hosted

Linux
macOS
Solaris
Windows

Linux

Data scheme

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.

XML can be used for describing objects metadata

Secondary indexes

yes

SQL

Support of SQL

SQL-99 for query and DML statements

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

C++ API
Java API

Supported programming languages

Java
JavaScript
Objective-C

.Net
C++
Java
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

Triggers

Callbacks are triggered when data changes

yes, event driven architecture

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

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

Consistency level configurable: ALL, QUORUM, ANY

Foreign keys

Referential integrity

Transaction concepts

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

yes

ACID

yes

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

Role-based access control

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.