DBMS > AlaSQL vs. EJDB vs. Graph Engine vs. HyperSQL vs. SQLite

System Properties Comparison AlaSQL vs. EJDB vs. Graph Engine vs. HyperSQL vs. SQLite

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Document store

Graph DBMS
Key-value store

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	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	3.49
Rank	#87	Overall
	#47	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

alasql.org

github.com/Softmotions/ejdb

www.graphengine.io

hsqldb.org

www.sqlite.org

Technical documentation

github.com/AlaSQL/alasql

github.com/Softmotions/ejdb/blob/master/README.md

www.graphengine.io/docs/manual

hsqldb.org/web/hsqlDocsFrame.html

www.sqlite.org/docs.html

Developer

Andrey Gershun & Mathias R. Wulff

Softmotions

Microsoft

Dwayne Richard Hipp

Initial release

2014

2012

2010

2001

2000

Current release

2.7.2, June 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

GPLv2

Open Source

MIT License

Open Source

based on BSD license

Open Source

Public Domain

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

.NET and C

Java

Server operating systems

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

server-less

.NET

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL

Support of SQL

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

yes

SQL-92 is not fully supported

APIs and other access methods

JavaScript API

in-process shared library

RESTful HTTP API

HTTP API

JDBC via HTTP
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

JavaScript

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C#
C++
F#
Visual Basic

All languages supporting JDBC/ODBC
Java

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Java, SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

typically not needed, however similar functionality with collection joins possible

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

Read/Write Locking

yes

via file-system locks

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

User concepts

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.