DBMS > AlaSQL vs. Amazon DocumentDB vs. HEAVY.AI vs. Riak TS vs. SAP HANA

System Properties Comparison AlaSQL vs. Amazon DocumentDB vs. HEAVY.AI vs. Riak TS vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

Primary database model

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.49
Rank	#259	Overall
	#40	Document stores
	#120	Relational DBMS

Score	1.89
Rank	#137	Overall
	#24	Document stores

Score	2.10
Rank	#126	Overall
	#61	Relational DBMS

Score	0.25
Rank	#308	Overall
	#26	Time Series DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Website

alasql.org

aws.amazon.com/documentdb

github.com/heavyai/heavydb
www.heavy.ai

www.sap.com/products/hana.html

Technical documentation

github.com/AlaSQL/alasql

aws.amazon.com/documentdb/resources

docs.heavy.ai

www.tiot.jp/riak-docs/riak/ts/latest

help.sap.com/hana

Developer

Andrey Gershun & Mathias R. Wulff

HEAVY.AI, Inc.

Open Source, formerly Basho Technologies

SAP

Initial release

2014

2019

2016

2015

2010

Current release

5.10, January 2022

3.0.0, September 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

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 CUDA

Erlang

Server operating systems

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

hosted

Linux

Linux
OS X

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

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

restricted

yes

SQL

Support of SQL

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

yes

yes, limited

yes

APIs and other access methods

JavaScript API

proprietary protocol using JSON (MongoDB compatible)

JDBC
ODBC
Thrift
Vega

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

JavaScript

Go
Java
JavaScript (Node.js)
PHP
Python

All languages supporting JDBC/ODBC/Thrift
Python

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

Erlang

SQLScript, R

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Round robin

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

Multi-source replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

typically not used, however similar functionality with DBRef possible

links between datasets can be stored

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

Atomic single-document 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

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

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.