DBMS > Google Cloud Firestore vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. TerminusDB

System Properties Comparison Google Cloud Firestore vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Globally distributed, horizontally scalable, multi-model database service

A Wide Column Store for rapid development using massive semi-structured datasets

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Graph DBMS

Secondary database models

Spatial DBMS

Document store
RDF store

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

Score	8.96
Rank	#48	Overall
	#8	Document stores

Score	29.85
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	4.92
Rank	#73	Overall
	#6	Wide column stores

Score	0.22
Rank	#323	Overall
	#28	Graph DBMS

Website

firebase.google.com/products/firestore

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

terminusdb.com

Technical documentation

firebase.google.com/docs/firestore

learn.microsoft.com/azure/cosmos-db

terminusdb.github.io/terminusdb/#

Developer

Google

Microsoft

DataChemist Ltd.

Initial release

2017

2014

2012

2018

Current release

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

hosted

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

SQL-like query language (WOQL)

APIs and other access methods

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

RESTful HTTP API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

JavaScript

yes

Triggers

yes, with Cloud Functions

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

In-memory capabilities

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

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

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.