DBMS > AlaSQL vs. HEAVY.AI vs. MySQL vs. RDFox

System Properties Comparison AlaSQL vs. HEAVY.AI vs. MySQL vs. RDFox

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

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

Widely used open source RDBMS

High performance knowledge graph and semantic reasoning engine

Primary database model

Document store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Graph DBMS
RDF store

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

Relational 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	1.41
Rank	#153	Overall
	#71	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.22
Rank	#305	Overall
	#25	Graph DBMS
	#15	RDF stores

Website

alasql.org

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

www.mysql.com

www.oxfordsemantic.tech

Technical documentation

github.com/AlaSQL/alasql

docs.heavy.ai

dev.mysql.com/doc

docs.oxfordsemantic.tech

Developer

Andrey Gershun & Mathias R. Wulff

HEAVY.AI, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Oxford Semantic Technologies

Initial release

2014

2016

1995

2017

Current release

5.10, January 2022

9.0.0, July 2024

6.0, Septermber 2022

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2; enterprise edition available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Cloud-based only

Only available as a cloud 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

C and C++

C++

Server operating systems

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

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Data scheme

schema-free

yes

RDF schemas

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.

yes

Secondary indexes

yes

SQL

Support of SQL

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

yes

with proprietary extensions

APIs and other access methods

JavaScript API

JDBC
ODBC
Thrift
Vega

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API
SPARQL 1.1

Supported programming languages

JavaScript

All languages supporting JDBC/ODBC/Thrift
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Round robin

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

Multi-source replication
Source-replica replication

replication via a shared file system

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate Consistency in stand-alone mode, Eventual Consistency in replicated setups

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Roles, resources, and access types

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.