DBMS > AlaSQL vs. Apache Drill vs. Galaxybase vs. Google BigQuery vs. H2

System Properties Comparison AlaSQL vs. Apache Drill vs. Galaxybase vs. Google BigQuery vs. H2

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Scalable, ACID-compliant native distributed parallel graph platform

Large scale data warehouse service with append-only tables

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Primary database model

Document store
Relational DBMS

Graph DBMS

Relational DBMS

Secondary database models

Spatial 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	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.00
Rank	#383	Overall
	#39	Graph DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Website

alasql.org

drill.apache.org

galaxybase.com

cloud.google.com/bigquery

www.h2database.com

Technical documentation

github.com/AlaSQL/alasql

drill.apache.org/docs

cloud.google.com/bigquery/docs

www.h2database.com/html/main.html

Developer

Andrey Gershun & Mathias R. Wulff

Apache Software Foundation

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Google

Thomas Mueller

Initial release

2014

2012

2017

2010

2005

Current release

1.20.3, January 2023

Nov 20, November 2021

2.2.220, July 2023

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

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 Java

Java

Server operating systems

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

Linux
OS X
Windows

Linux

hosted

All OS with a Java VM

Data scheme

schema-free

Strong typed schema

yes

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

SQL

Support of SQL

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

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JavaScript API

JDBC
ODBC
RESTful HTTP API

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

JavaScript

C++

Go
Java
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java

Server-side scripts

Stored procedures

user defined functions

user defined procedures and functions

user defined functions

in JavaScript

Java Stored Procedures and User-Defined Functions

Triggers

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

With clustering: 2 database servers on different computers operate on identical copies of a database

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

yes

only for local storage and DOM-storage

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

Depending on the underlying data source

yes

In-memory capabilities

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

yes

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Role-based access control

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

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.