DBMS > AlaSQL vs. Google BigQuery vs. JaguarDB vs. LokiJS vs. PouchDB

System Properties Comparison AlaSQL vs. Google BigQuery vs. JaguarDB vs. LokiJS vs. PouchDB

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Large scale data warehouse service with append-only tables

Performant, highly scalable DBMS for AI and IoT applications

In-memory JavaScript DBMS

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store
Vector DBMS

Document store

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	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	0.43
Rank	#264	Overall
	#42	Document stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

alasql.org

cloud.google.com/bigquery

www.jaguardb.com

github.com/techfort/LokiJS

pouchdb.com

Technical documentation

github.com/AlaSQL/alasql

cloud.google.com/bigquery/docs

www.jaguardb.com/support.html

techfort.github.io/LokiJS

pouchdb.com/guides

Developer

Andrey Gershun & Mathias R. Wulff

Google

DataJaguar, Inc.

Apache Software Foundation

Initial release

2014

2010

2015

2014

2012

Current release

3.3 July 2023

7.1.1, June 2019

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

GPL V3.0

Open Source

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++

the server part. Clients available in other languages

JavaScript

Server operating systems

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

hosted

Linux

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

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

yes

via views

SQL

Support of SQL

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

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

JavaScript API

RESTful HTTP/JSON API

JDBC
ODBC

JavaScript API

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

JavaScript

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript

Server-side scripts

Stored procedures

user defined functions

in JavaScript

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

none

Eventual 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

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

by using IndexedDB, WebSQL or LevelDB as backend

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

rights management via user accounts

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.