DBMS > Atos Standard Common Repository vs. Firebase Realtime Database vs. Heroic vs. Realm vs. Snowflake

System Properties Comparison Atos Standard Common Repository vs. Firebase Realtime Database vs. Heroic vs. Realm vs. Snowflake

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.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store
Key-value store

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

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	7.18
Rank	#52	Overall
	#8	Document stores

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

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

firebase.google.com/products/realtime-database

github.com/spotify/heroic

realm.io

www.snowflake.com

Technical documentation

firebase.google.com/docs/database

spotify.github.io/heroic

realm.io/docs

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Google

acquired by Google 2014

Spotify

Realm, acquired by MongoDB in May 2019

Snowflake Computing Inc.

Initial release

2016

2012

2014

Current release

1703

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

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

Server operating systems

Linux

hosted

Android
Backend: server-less
iOS
Windows

hosted

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

via Elasticsearch

yes

SQL

Support of SQL

yes

APIs and other access methods

LDAP

Android
iOS
JavaScript API
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Java
JavaScript
Objective-C

.Net
Java

with Android only
Objective-C
React Native
Swift

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

runs within the applications so server-side scripts are unnecessary

user defined functions

Triggers

yes

Callbacks are triggered when data changes

yes

Change Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

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
Immediate 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

In-Memory realm

User concepts

Access control

LDAP bind authentication

yes, based on authentication and database rules

yes

Users with fine-grained authorization concept, user roles and pluggable authentication

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.