DBMS > AlaSQL vs. Firebase Realtime Database vs. IRONdb vs. SQLite

System Properties Comparison AlaSQL vs. Firebase Realtime Database vs. IRONdb vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

JavaScript DBMS library

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Document store

Time Series DBMS

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

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

alasql.org

firebase.google.com/products/realtime-database

www.circonus.com/solutions/time-series-database/

www.sqlite.org

Technical documentation

github.com/AlaSQL/alasql

firebase.google.com/docs/database

docs.circonus.com/irondb/category/getting-started

www.sqlite.org/docs.html

Developer

Andrey Gershun & Mathias R. Wulff

Google

acquired by Google 2014

Circonus LLC.

Dwayne Richard Hipp

Initial release

2014

2012

2017

2000

Current release

V0.10.20, January 2018

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

MIT-License

commercial

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

JavaScript

C and C++

Server operating systems

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

hosted

Linux

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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.

Secondary indexes

yes

SQL

Support of SQL

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

SQL-92 is not fully supported

APIs and other access methods

JavaScript API

Android
iOS
JavaScript API
RESTful HTTP API

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

JavaScript

Java
JavaScript
Objective-C

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

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

limited functionality with using 'rules'

yes, in Lua

Triggers

yes

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic, metric affinity per node

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

configurable replication factor, datacenter aware

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate consistency per node, eventual consistency across nodes

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

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.