DBMS > AlaSQL vs. Atos Standard Common Repository vs. Firebase Realtime Database vs. Trafodion

System Properties Comparison AlaSQL vs. Atos Standard Common Repository vs. Firebase Realtime Database vs. Trafodion

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.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

JavaScript DBMS library

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.

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store
Relational DBMS

Document store
Key-value store

Document store

Relational DBMS

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

Score	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Website

alasql.org

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

firebase.google.com/products/realtime-database

trafodion.apache.org

Technical documentation

github.com/AlaSQL/alasql

firebase.google.com/docs/database

trafodion.apache.org/documentation.html

Developer

Andrey Gershun & Mathias R. Wulff

Atos Convergence Creators

Google

acquired by Google 2014

Apache Software Foundation, originally developed by HP

Initial release

2014

2016

2012

2014

Current release

1703

2.3.0, February 2019

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

Apache 2.0

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

JavaScript

Java

C++, Java

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

Linux

hosted

Linux

Data scheme

schema-free

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

SQL

Support of SQL

Close to SQL99, but no user access control, stored procedures and host language bindings.

yes

APIs and other access methods

JavaScript API

LDAP

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

JavaScript

All languages with LDAP bindings

Java
JavaScript
Objective-C

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Java Stored Procedures

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

yes

only for local storage and DOM-storage

Atomic execution of specific operations

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

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

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

Create a Marvel Database with SQL and Javascript, the easy way
2 July 2019, Towards Data Science

HarperDB - How and Why We Built It From The Ground Up on NodeJS
28 February 2021, hackernoon.com

Multi faceted data exploration in the browser using Leaflet and amCharts
3 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 Firebase may have exposed 125M records from misconfigurations
19 March 2024, SC Media

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

provided by Google News

Evaluating HTAP Databases for Machine Learning Applications
2 November 2016, KDnuggets

HP Throws Trafodion Hat into OLTP Hadoop Ring
14 July 2014, Datanami

Low-latency, distributed database architectures are critical for emerging fog applications
7 April 2022, Embedded Computing Design

provided by Google News

Share this page