DBMS > FatDB vs. Google Cloud Firestore vs. RavenDB vs. SAP HANA

System Properties Comparison FatDB vs. Google Cloud Firestore vs. RavenDB vs. SAP HANA

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.

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.

Open Source Operational and Transactional Enterprise NoSQL Document Database

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

firebase.google.com/products/firestore

ravendb.net

www.sap.com/products/hana.html

Technical documentation

firebase.google.com/docs/firestore

ravendb.net/docs

help.sap.com/hana

Developer

FatCloud

Google

Hibernating Rhinos

SAP

Initial release

2012

2017

2010

Current release

5.4, July 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Server operating systems

Windows

hosted

Linux
macOS
Raspberry Pi
Windows

Appliance or cloud-service

Data scheme

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

Via inetgration in SQL Server

SQL-like query language (RQL)

yes

APIs and other access methods

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

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

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

JDBC
ODBC

Supported programming languages

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

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

Server-side scripts

Stored procedures

yes

via applications

yes, Firebase Rules & Cloud Functions

yes

SQLScript, R

Triggers

yes

via applications

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

yes

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

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID, Cluster-wide transaction available

ACID

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.

yes

User concepts

Access control

Can implement custom security layer via applications

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

Authorization levels configured per client per database

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.