DBMS > AlaSQL vs. Apache Drill vs. Drizzle vs. SQLite vs. WakandaDB

System Properties Comparison AlaSQL vs. Apache Drill vs. Drizzle vs. SQLite vs. WakandaDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

JavaScript DBMS library

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Widely used embeddable, in-process RDBMS

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Document store
Relational DBMS

Relational DBMS

Object oriented 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.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

Technical documentation

github.com/AlaSQL/alasql

drill.apache.org/docs

www.sqlite.org/docs.html

wakanda.github.io/doc

Developer

Andrey Gershun & Mathias R. Wulff

Apache Software Foundation

Drizzle project, originally started by Brian Aker

Dwayne Richard Hipp

Wakanda SAS

Initial release

2014

2012

2008

2000

2012

Current release

1.20.3, January 2023

7.2.4, September 2012

3.45.3 (15 April 2024), April 2024

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

MIT-License

Open Source

Apache Version 2

Open Source

GNU GPL

Open Source

Public Domain

Open Source

AGPLv3, extended commercial license 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.

Implementation language

JavaScript

C++

C++, JavaScript

Server operating systems

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

Linux
OS X
Windows

FreeBSD
Linux
OS X

server-less

Linux
OS X
Windows

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

SQL

Support of SQL

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

SQL SELECT statement is SQL:2003 compliant

yes

with proprietary extensions

yes

SQL-92 is not fully supported

APIs and other access methods

JavaScript API

JDBC
ODBC
RESTful HTTP API

JDBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

RESTful HTTP API

Supported programming languages

JavaScript

C++

C
C++
Java
PHP

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

JavaScript

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

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.