DBMS > AlaSQL vs. Amazon Redshift vs. Graph Engine vs. Machbase Neo vs. MaxDB

System Properties Comparison AlaSQL vs. Amazon Redshift vs. Graph Engine vs. Machbase Neo vs. MaxDB

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Large scale data warehouse service for use with business intelligence tools

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

TimeSeries DBMS for AIoT and BigData

A robust and reliable RDBMS optimized to run all major SAP solutions

Primary database model

Document store
Relational DBMS

Relational DBMS

Graph DBMS
Key-value store

Time Series DBMS

Relational 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	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Website

alasql.org

aws.amazon.com/redshift

www.graphengine.io

machbase.com

maxdb.sap.com

Technical documentation

github.com/AlaSQL/alasql

docs.aws.amazon.com/redshift

www.graphengine.io/docs/manual

machbase.com/dbms

maxdb.sap.com/documentation

Developer

Andrey Gershun & Mathias R. Wulff

Amazon (based on PostgreSQL)

Microsoft

Machbase

SAP, acquired from Software AG (Adabas-D) in 1997

Initial release

2014

2012

2010

2013

1984

Current release

V8.0, August 2023

7.9.10.12, February 2024

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

MIT License

commercial

free test version available

commercial

Limited community edition free

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

.NET and C

C++

Server operating systems

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

hosted

.NET

Linux
macOS
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

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

restricted

yes

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-like query language

yes

APIs and other access methods

JavaScript API

JDBC
ODBC

RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

ADO.NET
JDBC
ODBC
WebDAV

Supported programming languages

JavaScript

All languages supporting JDBC/ODBC

C#
C++
F#
Visual Basic

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.Net
C#
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

selectable replication factor

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

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

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

volatile and lookup table

User concepts

Access control

fine grained access rights according to SQL-standard

simple password-based access control

fine grained access rights according to SQL-standard

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.