DBMS > Firebase Realtime Database vs. MongoDB

System Properties Comparison Firebase Realtime Database vs. MongoDB

Please select another system to include it in the comparison.

Our visitors often compare Firebase Realtime Database and MongoDB with Redis, MySQL and Amazon DynamoDB.

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.

One of the most popular document stores available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Document store

Secondary database models

Spatial DBMS
Search engine

integrated Lucene index, currently in MongoDB Atlas only.
Time Series DBMS

Time Series Collections introduced in Release 5.0
Vector DBMS

currently available in the MongoDB Atlas cloud service only

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

Score	13.43
Rank	#39	Overall
	#6	Document stores

Score	402.51
Rank	#5	Overall
	#1	Document stores

Website

firebase.google.com/products/realtime-database

www.mongodb.com

Technical documentation

firebase.google.com/docs/database

www.mongodb.com/docs/manual

Developer

Google

acquired by Google 2014

MongoDB, Inc

Initial release

2012

2009

Current release

7.0.5, January 2024

License

Commercial or Open Source

commercial

Open Source

MongoDB Inc.'s Server Side Public License v1. Prior versions were published under GNU AGPL v3.0. Commercial licenses are also available.

Cloud-based only

Only available as a cloud service

yes

MongoDB available as DBaaS (MongoDB Atlas)

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Data scheme

schema-free

Although schema-free, documents of the same collection often follow the same structure. Optionally impose all or part of a schema by defining a JSON schema.

Typing

predefined data types such as float or date

yes

string, integer, double, decimal, boolean, date, object_id, geospatial

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

Read-only SQL queries via the MongoDB Atlas SQL Interface

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

GraphQL
HTTP REST
Prisma
proprietary protocol using JSON

Supported programming languages

Java
JavaScript
Objective-C

Actionscript

unofficial driver
C
C#
C++
Clojure

unofficial driver
ColdFusion

unofficial driver
D

unofficial driver
Dart

unofficial driver
Delphi

unofficial driver
Erlang
Go
Groovy

unofficial driver
Haskell
Java
JavaScript
Kotlin
Lisp

unofficial driver
Lua

unofficial driver
MatLab

unofficial driver
Perl
PHP
PowerShell

unofficial driver
Prolog

unofficial driver
Python
R

unofficial driver
Ruby
Rust
Scala
Smalltalk

unofficial driver
Swift

Server-side scripts

Stored procedures

limited functionality with using 'rules'

JavaScript

Triggers

Callbacks are triggered when data changes

yes

in MongoDB Atlas only

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioned by hashed, ranged, or zoned sharding keys. Live resharding allows users to change their shard keys as an online operation with zero downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-Source deployments with MongoDB Atlas Global Clusters
Source-replica replication

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

Eventual Consistency

can be individually decided for each read operation
Immediate Consistency

default behaviour

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

Transaction concepts

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

yes

Multi-document ACID Transactions with snapshot isolation

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional, enabled by default

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

In-memory storage engine introduced with MongoDB version 3.2

User concepts

Access control

yes, based on authentication and database rules

Access rights for users and roles

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.