DBMS > Dragonfly vs. EXASOL vs. JaguarDB vs. Snowflake vs. WakandaDB

System Properties Comparison Dragonfly vs. EXASOL vs. JaguarDB vs. Snowflake vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Performant, highly scalable DBMS for AI and IoT applications

Cloud-based data warehousing service for structured and semi-structured data

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

Primary database model

Key-value store

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Object oriented DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.41
Rank	#266	Overall
	#38	Key-value stores

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

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

Technical documentation

www.dragonflydb.io/docs

www.exasol.com/resources

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

wakanda.github.io/doc

Developer

DragonflyDB team and community contributors

Exasol

DataJaguar, Inc.

Snowflake Computing Inc.

Wakanda SAS

Initial release

2023

2000

2015

2014

2012

Current release

1.0, March 2023

3.3 July 2023

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

BSL 1.1

commercial

Open Source

GPL V3.0

commercial

Open Source

AGPLv3, extended commercial license available

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

C++

the server part. Clients available in other languages

C++, JavaScript

Server operating systems

Linux

hosted

Linux
OS X
Windows

Data scheme

scheme-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

.Net
JDBC
ODBC
WebSocket

JDBC
ODBC

CLI Client
JDBC
ODBC

RESTful HTTP API

Supported programming languages

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

Java
Lua
Python
R

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

JavaScript

Server-side scripts

Stored procedures

Lua

user defined functions

yes

Triggers

publish/subscribe channels provide some trigger functionality

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of command blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

Durability

Support for making data persistent

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

Access rights for users, groups and roles according to SQL-standard

rights management via user accounts

Users with fine-grained authorization concept, user roles and pluggable authentication

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.