DBMS > Atos Standard Common Repository vs. Google Cloud Firestore vs. Percona Server for MongoDB vs. SpatiaLite

System Properties Comparison Atos Standard Common Repository vs. Google Cloud Firestore vs. Percona Server for MongoDB vs. SpatiaLite

Please select another system to include it in the comparison.

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.

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Spatial extension of SQLite

Primary database model

Document store
Key-value store

Document store

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

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

firebase.google.com/products/firestore

www.percona.com/mongodb/software/percona-server-for-mongodb

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

firebase.google.com/docs/firestore

docs.percona.com/percona-distribution-for-mongodb

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Atos Convergence Creators

Google

Percona

Alessandro Furieri

Initial release

2016

2017

2015

2008

Current release

1703

3.4.10-2.10, November 2017

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

GPL Version 2

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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

C++

Server operating systems

Linux

hosted

Linux

server-less

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

optional

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

SQL

Support of SQL

yes

APIs and other access methods

LDAP

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

proprietary protocol using JSON

Supported programming languages

All languages with LDAP bindings

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

JavaScript

Triggers

yes

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

yes

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

via In-Memory Engine

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 for users and roles

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

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

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

Google's Cloud Firestore is now generally available
31 January 2019, ZDNet

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

Google Cloud adds vector support to all its database offerings
29 February 2024, InfoWorld

provided by Google News

5 Reasons to Run MongoDB on Kubernetes
6 March 2024, The New Stack

Unlock MongoDB's Full Potential: Ensuring Post-Upgrade Success
22 February 2024, The New Stack

FerretDB goes GA: Gives you MongoDB, without the MongoDB...
15 May 2023, The Stack

Percona launches management system aimed at open-source databases
17 May 2022, The Register

6 keys to MongoDB database security
22 May 2019, InfoWorld

provided by Google News

Share this page