DBMS > AlaSQL vs. Hazelcast vs. Kinetica vs. MySQL

System Properties Comparison AlaSQL vs. Hazelcast vs. Kinetica vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

A widely adopted in-memory data grid

Fully vectorized database across both GPUs and CPUs

Widely used open source RDBMS

Primary database model

Document store
Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS
Time Series DBMS

Document store
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	6.87
Rank	#55	Overall
	#6	Key-value stores

Score	0.69
Rank	#234	Overall
	#107	Relational DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

github.com/AlaSQL/alasql

hazelcast.org/imdg/docs

docs.kinetica.com

dev.mysql.com/doc

Developer

Andrey Gershun & Mathias R. Wulff

Hazelcast

Kinetica

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2014

2008

2012

1995

Current release

5.3.6, November 2023

7.1, August 2021

8.3.0, January 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

JavaScript

Java

C, C++

C and C++

Server operating systems

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

All OS with a Java VM

Linux

FreeBSD
Linux
OS X
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.

yes

the object must implement a serialization strategy

yes

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

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

JavaScript API

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

JavaScript

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

C++
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

user defined functions

yes

proprietary syntax

Triggers

yes

Events

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Replicated Map

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

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

one or two-phase-commit; repeatable reads; read commited

ACID

not for MyISAM storage engine

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

GPU vRAM or System RAM

yes

User concepts

Access control

Role-based access control

Access rights for users and roles on table level

Users with fine-grained authorization concept

no user groups or roles

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.