DBMS > AlaSQL vs. Google BigQuery vs. HarperDB vs. Infobright

System Properties Comparison AlaSQL vs. Google BigQuery vs. HarperDB vs. Infobright

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Large scale data warehouse service with append-only tables

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Primary database model

Document store
Relational DBMS

Relational DBMS

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

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Website

alasql.org

cloud.google.com/bigquery

www.harperdb.io

ignitetech.com/softwarelibrary/infobrightdb

Technical documentation

github.com/AlaSQL/alasql

cloud.google.com/bigquery/docs

docs.harperdb.io/docs

Developer

Andrey Gershun & Mathias R. Wulff

Google

HarperDB

Ignite Technologies Inc.; formerly InfoBright Inc.

Initial release

2014

2010

2017

2005

Current release

3.1, August 2021

License

Commercial or Open Source

Open Source

MIT-License

commercial

free community edition available

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

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

Node.js

Server operating systems

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

hosted

Linux
OS X

Linux
Windows

Data scheme

schema-free

yes

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data types

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

Knowledge Grid Technology used instead

SQL

Support of SQL

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

yes

SQL-like data manipulation statements

yes

APIs and other access methods

JavaScript API

RESTful HTTP/JSON API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

ADO.NET
JDBC
ODBC

Supported programming languages

JavaScript

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Custom Functions

since release 3.1

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

A table resides as a whole on one (or more) nodes in a cluster

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

the nodes on which a table resides can be defined

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

Since BigQuery is designed for querying data

Atomic execution of specific operations

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

yes, using LMDB

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

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

Google Cloud Identity & Access Management (IAM)

Access rights for users and roles

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.