DBMS > Atos Standard Common Repository vs. Datomic vs. Firebase Realtime Database vs. Heroic vs. SQLite

System Properties Comparison Atos Standard Common Repository vs. Datomic vs. Firebase Realtime Database vs. Heroic vs. SQLite

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Key-value store

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

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

www.datomic.com

firebase.google.com/products/realtime-database

github.com/spotify/heroic

www.sqlite.org

Technical documentation

docs.datomic.com

firebase.google.com/docs/database

spotify.github.io/heroic

www.sqlite.org/docs.html

Developer

Atos Convergence Creators

Cognitect

Google

acquired by Google 2014

Spotify

Dwayne Richard Hipp

Initial release

2016

2012

2014

2000

Current release

1703

1.0.7075, December 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

Apache 2.0

Open Source

Public Domain

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

Java, Clojure

Java

Server operating systems

Linux

All OS with a Java VM

hosted

server-less

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

optional

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

APIs and other access methods

LDAP

RESTful HTTP API

Android
iOS
JavaScript API
RESTful HTTP API

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

All languages with LDAP bindings

Clojure
Java

Java
JavaScript
Objective-C

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Transaction Functions

limited functionality with using 'rules'

Triggers

yes

By using transaction functions

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

But extensive use of caching in the application peers

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

yes

none

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

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

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.