DBMS > AlaSQL vs. Amazon Redshift vs. Apache Drill vs. Riak TS

System Properties Comparison AlaSQL vs. Amazon Redshift vs. Apache Drill vs. Riak TS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Large scale data warehouse service for use with business intelligence tools

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

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store
Relational DBMS

Time Series 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	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

alasql.org

aws.amazon.com/redshift

drill.apache.org

Technical documentation

github.com/AlaSQL/alasql

docs.aws.amazon.com/redshift

drill.apache.org/docs

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

Developer

Andrey Gershun & Mathias R. Wulff

Amazon (based on PostgreSQL)

Apache Software Foundation

Open Source, formerly Basho Technologies

Initial release

2014

2012

2015

Current release

1.20.3, January 2023

3.0.0, September 2022

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

Apache Version 2

Open Source

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

Erlang

Server operating systems

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

hosted

Linux
OS X
Windows

Linux
OS X

Data scheme

schema-free

yes

schema-free

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

restricted

SQL

Support of SQL

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

yes

does not fully support an SQL-standard

SQL SELECT statement is SQL:2003 compliant

yes, limited

APIs and other access methods

JavaScript API

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

HTTP API
Native Erlang Interface

Supported programming languages

JavaScript

All languages supporting JDBC/ODBC

C++

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

user defined functions

in Python

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

none

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

links between datasets can be stored

Transaction concepts

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

yes

only for local storage and DOM-storage

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

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

User concepts

Access control

fine grained access rights according to SQL-standard

Depending on the underlying data source

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.