DBMS > AlaSQL vs. Google Cloud Datastore vs. Graph Engine vs. SAP HANA

System Properties Comparison AlaSQL vs. Google Cloud Datastore vs. Graph Engine vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Primary database model

Document store
Relational DBMS

Document store

Graph DBMS
Key-value store

Relational DBMS

Secondary database models

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.42
Rank	#264	Overall
	#42	Document stores
	#122	Relational DBMS

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	0.56
Rank	#241	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

alasql.org

cloud.google.com/datastore

www.graphengine.io

www.sap.com/products/hana.html

Technical documentation

github.com/AlaSQL/alasql

cloud.google.com/datastore/docs

www.graphengine.io/docs/manual

help.sap.com/hana

Developer

Andrey Gershun & Mathias R. Wulff

Google

Microsoft

SAP

Initial release

2014

2008

2010

Current release

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

MIT 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

.NET and C

Server operating systems

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

hosted

.NET

Appliance or cloud-service

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

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

RESTful HTTP API

JDBC
ODBC

Supported programming languages

JavaScript

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

C#
C++
F#
Visual Basic

Server-side scripts

Stored procedures

using Google App Engine

yes

SQLScript, R

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication using Paxos

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

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

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.