DBMS > AlaSQL vs. Apache IoTDB vs. Dgraph vs. Ehcache vs. MySQL

System Properties Comparison AlaSQL vs. Apache IoTDB vs. Dgraph vs. Ehcache vs. MySQL

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

Distributed and scalable native Graph DBMS

A widely adopted Java cache with tiered storage options

Widely used open source RDBMS

Primary database model

Document store
Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.51
Rank	#256	Overall
	#40	Document stores
	#118	Relational DBMS

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

github.com/AlaSQL/alasql

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

dgraph.io/docs

www.ehcache.org/documentation

dev.mysql.com/doc

Developer

Andrey Gershun & Mathias R. Wulff

Apache Software Foundation

Dgraph Labs, Inc.

Terracotta Inc, owned by Software AG

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2014

2018

2016

2009

1995

Current release

1.1.0, April 2023

3.10.0, March 2022

8.4.0, April 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2.0

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

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 and C++

Server operating systems

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

All OS with a Java VM (>= 1.8)

Linux
OS X
Windows

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

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.

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

yes

with proprietary extensions

APIs and other access methods

JavaScript API

JDBC
Native API

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

JCache

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

JavaScript

C
C#
C++
Go
Java
Python
Scala

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java

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

proprietary syntax

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

yes

Sharding

by using Terracotta Server

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

Synchronous replication via Raft

yes

by using Terracotta Server

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

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

ACID

yes

supports JTA and can work as an XA resource

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

using a tiered cache-storage approach

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

yes

Planned for future releases

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.