DBMS > AlaSQL vs. Google BigQuery vs. Google Cloud Datastore vs. H2 vs. KeyDB

System Properties Comparison AlaSQL vs. Google BigQuery vs. Google Cloud Datastore vs. H2 vs. KeyDB

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Large scale data warehouse service with append-only tables

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Primary database model

Document store
Relational DBMS

Secondary database models

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Website

alasql.org

cloud.google.com/bigquery

cloud.google.com/datastore

www.h2database.com

github.com/Snapchat/KeyDB
keydb.dev

Technical documentation

github.com/AlaSQL/alasql

cloud.google.com/bigquery/docs

cloud.google.com/datastore/docs

www.h2database.com/html/main.html

docs.keydb.dev

Developer

Andrey Gershun & Mathias R. Wulff

Google

Thomas Mueller

EQ Alpha Technology Ltd.

Initial release

2014

2010

2008

2005

2019

Current release

2.2.220, July 2023

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

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

Open Source

BSD-3

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

C++

Server operating systems

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

hosted

All OS with a Java VM

Linux

Data scheme

schema-free

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

SQL

Support of SQL

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

yes

SQL-like query language (GQL)

yes

APIs and other access methods

JavaScript API

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protoco

Supported programming languages

JavaScript

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Java

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in JavaScript

using Google App Engine

Java Stored Procedures and User-Defined Functions

Lua

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

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

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

simple password-based access control and ACL

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.