DBMS > FatDB vs. Google BigQuery vs. Google Cloud Firestore vs. RethinkDB

System Properties Comparison FatDB vs. Google BigQuery vs. Google Cloud Firestore vs. RethinkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Large scale data warehouse service with append-only tables

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.

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

Primary database model

Document store
Key-value store

Relational DBMS

Document store

Secondary database models

Spatial DBMS

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	2.66
Rank	#107	Overall
	#20	Document stores

Website

cloud.google.com/bigquery

firebase.google.com/products/firestore

rethinkdb.com

Technical documentation

cloud.google.com/bigquery/docs

firebase.google.com/docs/firestore

rethinkdb.com/docs

Developer

FatCloud

Google

The Linux Foundation

since July 2017

Initial release

2012

2010

2017

2009

Current release

2.4.1, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

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++

Server operating systems

Windows

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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

Via inetgration in SQL Server

yes

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

RESTful HTTP/JSON API

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

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Server-side scripts

Stored procedures

yes

via applications

user defined functions

in JavaScript

yes, Firebase Rules & Cloud Functions

Triggers

yes

via applications

yes, with Cloud Functions

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

range based

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

yes

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

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.

User concepts

Access control

Can implement custom security layer via applications

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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

yes

users and table-level permissions

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.