DBMS > AlaSQL vs. Firebase Realtime Database vs. Hazelcast vs. RavenDB vs. SQLite

System Properties Comparison AlaSQL vs. Firebase Realtime Database vs. Hazelcast vs. RavenDB vs. SQLite

Editorial information provided by DB-Engines

Name

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 widely adopted in-memory data grid

Open Source Operational and Transactional Enterprise NoSQL Document Database

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

alasql.org

firebase.google.com/products/realtime-database

hazelcast.com

ravendb.net

www.sqlite.org

Technical documentation

github.com/AlaSQL/alasql

firebase.google.com/docs/database

hazelcast.org/imdg/docs

ravendb.net/docs

www.sqlite.org/docs.html

Developer

Andrey Gershun & Mathias R. Wulff

Google

acquired by Google 2014

Hazelcast

Hibernating Rhinos

Dwayne Richard Hipp

Initial release

2014

2012

2008

2010

2000

Current release

5.3.6, November 2023

5.4, July 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

AGPL version 3, commercial license available

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

Java

Server operating systems

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

hosted

All OS with a Java VM

Linux
macOS
Raspberry Pi
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

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

the object must implement a serialization strategy

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

SQL-like query language (RQL)

yes

SQL-92 is not fully supported

APIs and other access methods

JavaScript API

Android
iOS
JavaScript API
RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

JavaScript

Java
JavaScript
Objective-C

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Event Listeners, Executor Services

yes

Triggers

yes

Callbacks are triggered when data changes

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Replicated Map

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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 or Eventual Consistency selectable by user

Raft Consensus Algorithm

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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

one or two-phase-commit; repeatable reads; read commited

ACID, Cluster-wide transaction available

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

Role-based access control

Authorization levels configured per client per database

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.