DBMS > AlaSQL vs. BaseX vs. H2GIS vs. Microsoft Azure SQL Database vs. SQLite

System Properties Comparison AlaSQL vs. BaseX vs. H2GIS vs. Microsoft Azure SQL Database vs. SQLite

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

Spatial extension of H2

Database as a Service offering with high compatibility to Microsoft SQL Server

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Native XML DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

Document store
Graph DBMS
Spatial 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	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

alasql.org

basex.org

www.h2gis.org

azure.microsoft.com/en-us/products/azure-sql/database

www.sqlite.org

Technical documentation

github.com/AlaSQL/alasql

docs.basex.org

www.h2gis.org/docs/home

docs.microsoft.com/en-us/azure/azure-sql

www.sqlite.org/docs.html

Developer

Andrey Gershun & Mathias R. Wulff

BaseX GmbH

CNRS

Microsoft

Dwayne Richard Hipp

Initial release

2014

2007

2013

2010

2000

Current release

10.7, August 2023

V12

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

BSD license

Open Source

LGPL 3.0

commercial

Open Source

Public Domain

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

Java

C++

Server operating systems

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

Linux
OS X
Windows

hosted

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

XQuery supports types

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.

yes

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

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

ADO.NET
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

JavaScript

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

Java

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

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

based on H2

Transact SQL

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

based on H2

yes, with always 3 replicas available

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

Transaction concepts

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

yes

only for local storage and DOM-storage

multiple readers, single writer

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

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

Users with fine-grained authorization concept on 4 levels

yes

based on H2

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.