DBMS > BigObject vs. Cachelot.io vs. Firebase Realtime Database vs. GeoMesa vs. Realm

System Properties Comparison BigObject vs. Cachelot.io vs. Firebase Realtime Database vs. GeoMesa vs. Realm

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

In-memory caching system

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.

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Website

bigobject.io

cachelot.io

firebase.google.com/products/realtime-database

www.geomesa.org

realm.io

Technical documentation

docs.bigobject.io

firebase.google.com/docs/database

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

realm.io/docs

Developer

BigObject, Inc.

Google

acquired by Google 2014

CCRi and others

Realm, acquired by MongoDB in May 2019

Initial release

2015

2012

2014

Current release

4.0.5, February 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

Simplified BSD License

commercial

Open Source

Apache License 2.0

Open Source

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

C++

Scala

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

FreeBSD
Linux
OS X

hosted

Android
Backend: server-less
iOS
Windows

Data scheme

yes

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

Memcached protocol

Android
iOS
JavaScript API
RESTful HTTP API

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

Java
JavaScript
Objective-C

.Net
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

Lua

limited functionality with using 'rules'

runs within the applications so server-side scripts are unnecessary

Triggers

Callbacks are triggered when data changes

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

automatically between fact table and dimension tables

Transaction concepts

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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.

yes

depending on storage layer

yes

In-Memory realm

User concepts

Access control

yes, based on authentication and database rules

yes

depending on the DBMS used for storage

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.

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

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

Recent citations in the news

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

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

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

MongoDB aims to unify developer experience with launch of MongoDB Cloud
9 June 2020, diginomica

Danish CEO explains Silicon Valley learning curve for European entrepreneurs - San Francisco Business Times
6 October 2016, The Business Journals

Is Swift the Future of Server-side Development?
12 September 2017, Solutions Review

Java Synthetic Methods — What are these? | by Vaibhav Singh
27 February 2021, DataDrivenInvestor

Kotlin Programming Language Will Surpass Java On Android Next Year
15 October 2017, Fossbytes

provided by Google News

Share this page