DBMS > Atos Standard Common Repository vs. GeoMesa vs. Google Cloud Firestore vs. SpatiaLite

System Properties Comparison Atos Standard Common Repository vs. GeoMesa vs. Google Cloud Firestore 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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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.

Spatial extension of SQLite

Primary database model

Document store
Key-value store

Spatial DBMS

Document store

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

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

www.geomesa.org

firebase.google.com/products/firestore

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

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

firebase.google.com/docs/firestore

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

Developer

Atos Convergence Creators

CCRi and others

Google

Alessandro Furieri

Initial release

2016

2014

2017

2008

Current release

1703

4.0.5, February 2024

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

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

Scala

C++

Server operating systems

Linux

hosted

server-less

Data scheme

Schema and schema-less with LDAP views

yes

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

Supported programming languages

All languages with LDAP bindings

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

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

Triggers

yes

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

depending on storage layer

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

depending on storage layer

yes

User concepts

Access control

LDAP bind authentication

yes

depending on the DBMS used for storage

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

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

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

Share this page