DBMS > AlaSQL vs. Dragonfly vs. SQL.JS vs. SQLite

System Properties Comparison AlaSQL vs. Dragonfly vs. SQL.JS vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

Port of SQLite to JavaScript

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational 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.41
Rank	#266	Overall
	#38	Key-value stores

Score	0.53
Rank	#252	Overall
	#116	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

alasql.org

github.com/dragonflydb/dragonfly
www.dragonflydb.io

sql.js.org

www.sqlite.org

Technical documentation

github.com/AlaSQL/alasql

www.dragonflydb.io/docs

sql.js.org/documentation/index.html

www.sqlite.org/docs.html

Developer

Andrey Gershun & Mathias R. Wulff

DragonflyDB team and community contributors

Alon Zakai

enhancements implemented by others

Dwayne Richard Hipp

Initial release

2014

2023

2012

2000

Current release

1.0, March 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

BSL 1.1

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

C++

JavaScript

Server operating systems

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

Linux

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

server-less

Data scheme

schema-free

scheme-free

yes

dynamic column types

Typing

predefined data types such as float or date

strings, hashes, lists, sets, sorted sets, bit arrays

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

yes

SQL-92 is not fully supported

APIs and other access methods

JavaScript API

Proprietary protocol

RESP - REdis Serialization Protocol

JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

JavaScript

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

JavaScript

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

Lua

Triggers

yes

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

none

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

Atomic execution of command blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

via file-system locks

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

except by serializing a db to a file

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

Password-based authentication

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.