DBMS > AlaSQL vs. Firebase Realtime Database vs. Google BigQuery vs. LokiJS vs. Warp 10

System Properties Comparison AlaSQL vs. Firebase Realtime Database vs. Google BigQuery vs. LokiJS vs. Warp 10

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.

Large scale data warehouse service with append-only tables

In-memory JavaScript DBMS

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store
Relational 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	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.49
Rank	#260	Overall
	#42	Document stores

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

alasql.org

firebase.google.com/products/realtime-database

cloud.google.com/bigquery

github.com/techfort/LokiJS

www.warp10.io

Technical documentation

github.com/AlaSQL/alasql

firebase.google.com/docs/database

cloud.google.com/bigquery/docs

techfort.github.io/LokiJS

www.warp10.io/content/02_Getting_started

Developer

Andrey Gershun & Mathias R. Wulff

Google

acquired by Google 2014

Google

SenX

Initial release

2014

2012

2010

2014

2015

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

Apache License 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

Server operating systems

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

hosted

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

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

via views

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

Android
iOS
JavaScript API
RESTful HTTP API

RESTful HTTP/JSON API

JavaScript API

HTTP API
Jupyter
WebSocket

Supported programming languages

JavaScript

Java
JavaScript
Objective-C

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

in JavaScript

View functions in JavaScript

yes

WarpScript

Triggers

yes

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

based on HBase

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

none

Immediate Consistency

based on HBase

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

Since BigQuery is designed for querying data

atomic operations within a single collection possible

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

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

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.