DBMS > FatDB vs. Google Cloud Firestore vs. IBM Cloudant vs. jBASE

System Properties Comparison FatDB vs. Google Cloud Firestore vs. IBM Cloudant vs. jBASE

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.

Database as a Service offering based on Apache CouchDB

A robust multi-value DBMS comprising development tools and middleware

Primary database model

Document store
Key-value store

Document store

Multivalue DBMS

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

Score	7.36
Rank	#53	Overall
	#9	Document stores

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Website

firebase.google.com/products/firestore

www.ibm.com/products/cloudant

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

Technical documentation

firebase.google.com/docs/firestore

cloud.ibm.com/docs/Cloudant

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

Developer

FatCloud

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Rocket Software (formerly Zumasys)

Initial release

2012

2017

2010

1991

Current release

5.7

License

Commercial or Open Source

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

Erlang

Server operating systems

Windows

hosted

AIX
Linux
Windows

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

optional

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.

yes

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

Embedded SQL for jBASE in BASIC

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

RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
Basic
Jabbascript
Java

Server-side scripts

Stored procedures

yes

via applications

yes, Firebase Rules & Cloud Functions

View functions (Map-Reduce) in JavaScript

yes

Triggers

yes

via applications

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

Multi-source replication
Source-replica 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

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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.

Access rights for users can be defined per database

Access rights can be defined down to the item level

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

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

show all

Recent citations in the news

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

Realtime vs Cloud Firestore: Which Firebase Database to go?
8 March 2024, Appinventiv

Google launches Cloud Firestore, a new document database for app developers
3 October 2017, TechCrunch

Google's Cloud-Native NoSQL Database Cloud Firestore Is Now Generally Available
8 February 2019, InfoQ.com

Firestore and Python | NoSQL on Google Cloud
7 August 2020, Towards Data Science

provided by Google News

Cloudant Best (and Worst) Practices — Part 1
18 March 2019, ibm.com

Intro to Enterprise Cloud Storage: How to Set Up a Cloudant Database
1 December 2014, Linux.com

IBM Expands Cloud Database Services with Kubernetes
26 September 2019, EnterpriseAI

IBM Code Engine and IBM Cloudant: Serverless Data and Infrastructure
16 August 2021, ibm.com

IBM to Purchase Cloudant Database as a service (DBaaS) Provider
22 March 2014, App Developer Magazine

provided by Google News

Temenos signs first customer in India
24 August 2009, Finextra

provided by Google News

Share this page