DBMS > FatDB vs. Firebird vs. Google Cloud Firestore vs. Oracle Coherence

System Properties Comparison FatDB vs. Firebird vs. Google Cloud Firestore vs. Oracle Coherence

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.

Firebird is an open source RDBMS forked from Borland's InterBase

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.

Oracles in-memory data grid solution

Primary database model

Document store
Key-value store

Relational DBMS

Document store

Key-value store

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

Score	24.77
Rank	#32	Overall
	#19	Relational DBMS

Score	9.25
Rank	#52	Overall
	#10	Document stores

Score	2.56
Rank	#114	Overall
	#21	Key-value stores

Website

www.firebirdsql.org

firebase.google.com/products/firestore

www.oracle.com/middleware/technologies/coherence.html

Technical documentation

www.firebirdsql.org/en/reference-manuals

firebase.google.com/docs/firestore

docs.oracle.com/en/middleware/standalone/coherence

Developer

FatCloud

Firebird Foundation

Google

Oracle

Initial release

2012

2000

As fork of Borland's InterBase

2017

2007

Current release

4.0.1, December 2021

12c, September 2016

License

Commercial or Open Source

commercial

Open Source

Initial Developer's Public License

commercial

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

Java

Server operating systems

Windows

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

hosted

All OS with a Java VM

Data scheme

schema-free

yes

schema-free

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

yes

APIs and other access methods

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

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

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

JCache
JPA
RESTful HTTP API

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

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

.Net
C++
Java

Server-side scripts

Stored procedures

yes

via applications

PSQL

yes, Firebase Rules & Cloud Functions

Triggers

yes

via applications

yes

yes, with Cloud Functions

yes

Live Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

available via 3rd party products

Multi-source replication

yes, with selectable consistency level

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

configurable

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

yes

Durability

Support for making data persistent

yes

optionally

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

Users with fine-grained authorization concept

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

authentification to access the cache via certificates or http basic authentication

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