DBMS > AlaSQL vs. Galaxybase vs. Google Cloud Datastore vs. H2 vs. SAP HANA

System Properties Comparison AlaSQL vs. Galaxybase vs. Google Cloud Datastore vs. H2 vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Scalable, ACID-compliant native distributed parallel graph platform

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.

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store
Relational DBMS

Graph DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
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	0.07
Rank	#377	Overall
	#40	Graph DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

alasql.org

galaxybase.com

cloud.google.com/datastore

www.h2database.com

www.sap.com/products/hana.html

Technical documentation

github.com/AlaSQL/alasql

cloud.google.com/datastore/docs

www.h2database.com/html/main.html

help.sap.com/hana

Developer

Andrey Gershun & Mathias R. Wulff

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

Google

Thomas Mueller

SAP

Initial release

2014

2017

2008

2005

2010

Current release

Nov 20, November 2021

2.2.220, July 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

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

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

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

hosted

All OS with a Java VM

Appliance or cloud-service

Data scheme

schema-free

Strong typed schema

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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-like query language (GQL)

yes

APIs and other access methods

JavaScript API

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

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

JDBC
ODBC

Supported programming languages

JavaScript

Go
Java
Python

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

Java

Server-side scripts

Stored procedures

user defined procedures and functions

using Google App Engine

Java Stored Procedures and User-Defined Functions

SQLScript, R

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

yes

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

yes

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

Foreign keys

Referential integrity

yes

Relationships in graphs

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

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

In-memory capabilities

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

yes

User concepts

Access control

Role-based access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

yes

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.