DBMS > Atos Standard Common Repository vs. Firebase Realtime Database vs. Riak TS vs. SpatiaLite

System Properties Comparison Atos Standard Common Repository vs. Firebase Realtime Database vs. Riak TS 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-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Spatial extension of SQLite

Primary database model

Document store
Key-value store

Document store

Time Series DBMS

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Score	1.56
Rank	#142	Overall
	#3	Spatial DBMS

Website

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

firebase.google.com/products/realtime-database

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

Technical documentation

firebase.google.com/docs/database

www.tiot.jp/riak-docs/riak/ts/latest

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

Developer

Atos Convergence Creators

Google

acquired by Google 2014

Open Source, formerly Basho Technologies

Alessandro Furieri

Initial release

2016

2012

2015

2008

Current release

1703

3.0.0, September 2022

5.0.0, August 2020

License

Commercial or Open Source

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

Erlang

C++

Server operating systems

Linux

hosted

Linux
OS X

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

restricted

yes

SQL

Support of SQL

yes, limited

yes

APIs and other access methods

LDAP

Android
iOS
JavaScript API
RESTful HTTP API

HTTP API
Native Erlang Interface

Supported programming languages

All languages with LDAP bindings

Java
JavaScript
Objective-C

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Erlang

Triggers

yes

Callbacks are triggered when data changes

yes

pre-commit hooks and post-commit hooks

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

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

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

User concepts

Access control

LDAP bind authentication

yes, based on authentication and database rules

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 Choose
8 March 2024, Appinventiv

Don't be like these 900+ websites and expose millions of passwords via Firebase
18 March 2024, The Register

Misconfigured Firebase instances leaked 19 million plaintext passwords
19 March 2024, BleepingComputer

Misconfigured firebase: A real-time cyber threat
18 January 2024, Atos

Google launches Firebase Genkit, a new open source framework for building AI-powered apps
14 May 2024, TechCrunch

provided by Google News

Is Riak A Good NoSQL Database Option For Enterprises?
1 July 2019, AIM

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Share this page