DBMS > AlaSQL vs. Amazon Redshift vs. Dragonfly vs. TerminusDB

System Properties Comparison AlaSQL vs. Amazon Redshift vs. Dragonfly vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

Large scale data warehouse service for use with business intelligence tools

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

Graph DBMS

Secondary database models

Document store
RDF store

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	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.49
Rank	#261	Overall
	#38	Key-value stores

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

alasql.org

aws.amazon.com/redshift

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

terminusdb.com

Technical documentation

github.com/AlaSQL/alasql

docs.aws.amazon.com/redshift

www.dragonflydb.io/docs

terminusdb.github.io/terminusdb/#

Developer

Andrey Gershun & Mathias R. Wulff

Amazon (based on PostgreSQL)

DragonflyDB team and community contributors

DataChemist Ltd.

Initial release

2014

2012

2023

2018

Current release

1.0, March 2023

11.0.0, January 2023

License

Commercial or Open Source

Open Source

MIT-License

commercial

Open Source

BSL 1.1

Open Source

GPL V3

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

C++

Prolog, Rust

Server operating systems

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

hosted

Linux

Data scheme

schema-free

yes

scheme-free

yes

Typing

predefined data types such as float or date

yes

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

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

restricted

SQL

Support of SQL

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

yes

does not fully support an SQL-standard

SQL-like query language (WOQL)

APIs and other access methods

JavaScript API

JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protocol

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

JavaScript

All languages supporting JDBC/ODBC

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
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

yes

Triggers

yes

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Atomic execution of command blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

in-memory journaling

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

Password-based authentication

Role-based access control

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.