DBMS > Atos Standard Common Repository vs. Dolt vs. Firebase Realtime Database vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. Dolt vs. Firebase Realtime Database vs. Yaacomo

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.

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

A MySQL compatible DBMS with Git-like versioning of data and schema

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

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

Primary database model

Document store
Key-value store

Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Website

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

github.com/dolthub/dolt
www.dolthub.com

firebase.google.com/products/realtime-database

yaacomo.com

Technical documentation

docs.dolthub.com

firebase.google.com/docs/database

Developer

Atos Convergence Creators

DoltHub Inc

Google

acquired by Google 2014

Q2WEB GmbH

Initial release

2016

2018

2012

2009

Current release

1703

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

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

Linux
macOS
Windows

hosted

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

yes

APIs and other access methods

LDAP

CLI Client
HTTP REST

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java
JavaScript
Objective-C

Server-side scripts

Stored procedures

yes

currently in alpha release

limited functionality with using 'rules'

Triggers

yes

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Source-replica replication

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

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

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

Only one user is configurable, and must be specified in the config file at startup

yes, based on authentication and database rules

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

Dolt- A Version Controlled Database
29 January 2024, iProgrammer

Top Data Version Control Tools for Machine Learning Research in 2023
24 July 2023, MarkTechPost

Dolt, a Relational Database with Git-Like Cloning Features
19 August 2020, The New Stack

Data Versioning at Scale: Chaos and Chaos Management
10 February 2023, InfoQ.com

25 Hot New Data Tools and What They DON'T Do
14 May 2020, Towards Data Science

provided by Google News

Realtime vs Cloud Firestore: Which Firebase Database to go?
8 March 2024, Appinventiv

Atos cybersecurity blog: Misconfigured Firebase: A real-time cyber threat
18 January 2024, Atos

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

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

Hundreds of Google Firebase websites might have leaked data online
19 March 2024, TechRadar

provided by Google News

Share this page