DBMS > Google Cloud Firestore vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. Valentina Server vs. Yaacomo

System Properties Comparison Google Cloud Firestore vs. IBM Cloudant vs. Microsoft Azure Cosmos DB vs. Valentina Server vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

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.

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

Object-relational database and reports server

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

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

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

firebase.google.com/products/firestore

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

www.valentina-db.net

yaacomo.com

Technical documentation

firebase.google.com/docs/firestore

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Paradigma Software

Q2WEB GmbH

Initial release

2017

2010

2014

1999

2009

Current release

5.7.5

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

hosted

Linux
OS X
Windows

Android
Linux
Windows

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

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

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

RESTful HTTP/JSON API

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

ODBC

JDBC
ODBC

Supported programming languages

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

View functions (Map-Reduce) in JavaScript

JavaScript

yes

Triggers

yes, with Cloud Functions

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

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

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

fine grained access rights according to SQL-standard

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.