DBMS > Atos Standard Common Repository vs. Google Cloud Firestore vs. Microsoft Azure Cosmos DB vs. SiriDB vs. Warp 10

System Properties Comparison Atos Standard Common Repository vs. Google Cloud Firestore vs. Microsoft Azure Cosmos DB vs. SiriDB vs. Warp 10

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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.

Globally distributed, horizontally scalable, multi-model database service

Open Source Time Series DBMS

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store
Key-value store

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series 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	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

firebase.google.com/products/firestore

azure.microsoft.com/services/cosmos-db

siridb.com

www.warp10.io

Technical documentation

firebase.google.com/docs/firestore

learn.microsoft.com/azure/cosmos-db

docs.siridb.com

www.warp10.io/content/02_Getting_started

Developer

Atos Convergence Creators

Google

Microsoft

Cesbit

SenX

Initial release

2016

2017

2014

2017

2015

Current release

1703

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Apache License 2.0

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

Java

Server operating systems

Linux

hosted

Linux

Linux
OS X
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

schema-free

Typing

predefined data types such as float or date

optional

yes

JSON types

yes

Numeric data

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

LDAP

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

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

HTTP API

HTTP API
Jupyter
WebSocket

Supported programming languages

All languages with LDAP bindings

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

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

JavaScript

yes

WarpScript

Triggers

yes

yes, with Cloud Functions

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Implicit feature of the cloud service

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes

Implicit feature of the cloud service

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

yes

Multi-item ACID transactions with snapshot isolation within a partition

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

LDAP bind authentication

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 can be defined down to the item level

simple rights management via user accounts

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.