DBMS > Dragonfly vs. EJDB vs. Netezza vs. Snowflake

System Properties Comparison Dragonfly vs. EJDB vs. Netezza vs. Snowflake

Please select another system to include it in the comparison.

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Data warehouse and analytics appliance part of IBM PureSystems

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

Primary database model

Key-value store

Document store

Relational DBMS

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

Score	0.44
Rank	#255	Overall
	#38	Key-value stores

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	7.56
Rank	#48	Overall
	#31	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

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

github.com/Softmotions/ejdb

www.ibm.com/products/netezza

www.snowflake.com

Technical documentation

www.dragonflydb.io/docs

github.com/Softmotions/ejdb/blob/master/README.md

docs.snowflake.net/manuals/index.html

Developer

DragonflyDB team and community contributors

Softmotions

IBM

Snowflake Computing Inc.

Initial release

2023

2012

2000

2014

Current release

1.0, March 2023

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

GPLv2

commercial

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

Server operating systems

Linux

server-less

Linux

included in appliance

hosted

Data scheme

scheme-free

schema-free

yes

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

Typing

predefined data types such as float or date

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

yes

string, integer, double, bool, date, object_id

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

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

in-process shared library

JDBC
ODBC
OLE DB

CLI Client
JDBC
ODBC

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

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C
C++
Fortran
Java
Lua
Perl
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Lua

yes

user defined functions

Triggers

publish/subscribe channels provide some trigger functionality

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

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

Read/Write Locking

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

Users with fine-grained authorization concept

Users with fine-grained authorization concept, user roles and pluggable 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.