DBMS > Atos Standard Common Repository vs. BigObject vs. Google Cloud Firestore vs. SpaceTime vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. BigObject vs. Google Cloud Firestore vs. SpaceTime vs. Yaacomo

Editorial information provided by DB-Engines

Name

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

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

Description

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

Analytic DBMS for real-time computations and queries

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.

SpaceTime is a spatio-temporal DBMS with a focus on performance.

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

Primary database model

Document store
Key-value store

Relational DBMS

a hierachical model (tree) can be imposed

Document store

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Website

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

bigobject.io

firebase.google.com/products/firestore

www.mireo.com/spacetime

yaacomo.com

Technical documentation

docs.bigobject.io

firebase.google.com/docs/firestore

Developer

Atos Convergence Creators

BigObject, Inc.

Google

Mireo

Q2WEB GmbH

Initial release

2016

2015

2017

2020

2009

Current release

1703

License

Commercial or Open Source

commercial

free community edition available

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

Java

C++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

hosted

Linux

Android
Linux
Windows

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

SQL-like DML and DDL statements

A subset of ANSI SQL is implemented

yes

APIs and other access methods

LDAP

fluentd
ODBC
RESTful HTTP API

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

RESTful HTTP API

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

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

C#
C++
Python

Server-side scripts

Stored procedures

Lua

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

none

Sharding

Fixed-grid hypercubes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication

Real-time block device replication (DRBD)

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

none

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

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

Read/write lock on objects (tables, trees)

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.

yes

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.

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

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google 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 Firebase gets AI extensions, opens up its marketplace
10 May 2023, TechCrunch

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

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

provided by Google News

Share this page