DBMS > AlaSQL vs. Dragonfly vs. EventStoreDB vs. Infobright vs. RocksDB

System Properties Comparison AlaSQL vs. Dragonfly vs. EventStoreDB vs. Infobright vs. RocksDB

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

Industrial-strength, open-source database solution built from the ground up for event sourcing.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document 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	1.10
Rank	#179	Overall
	#1	Event Stores

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

alasql.org

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

www.eventstore.com

ignitetech.com/softwarelibrary/infobrightdb

rocksdb.org

Technical documentation

github.com/AlaSQL/alasql

www.dragonflydb.io/docs

developers.eventstore.com

github.com/facebook/rocksdb/wiki

Developer

Andrey Gershun & Mathias R. Wulff

DragonflyDB team and community contributors

Event Store Limited

Ignite Technologies Inc.; formerly InfoBright Inc.

Facebook, Inc.

Initial release

2014

2023

2012

2005

2013

Current release

1.0, March 2023

21.2, February 2021

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT-License

Open Source

BSL 1.1

Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

BSD

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++

Server operating systems

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

Linux

Linux
Windows

Linux

Data scheme

schema-free

scheme-free

yes

schema-free

Typing

predefined data types such as float or date

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

Knowledge Grid Technology used instead

SQL

Support of SQL

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

yes

APIs and other access methods

JavaScript API

Proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
JDBC
ODBC

C++ API
Java API

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

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Lua

Triggers

yes

publish/subscribe channels provide some trigger functionality

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

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

Atomic execution of command blocks and scripts

ACID

yes

Concurrency

Support for concurrent manipulation of data

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 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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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.