DBMS > Dragonfly vs. EJDB vs. MySQL vs. Newts

System Properties Comparison Dragonfly vs. EJDB vs. MySQL vs. Newts

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)

Widely used open source RDBMS

Time Series DBMS based on Cassandra

Primary database model

Key-value store

Document store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

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

github.com/Softmotions/ejdb

www.mysql.com

opennms.github.io/newts

Technical documentation

www.dragonflydb.io/docs

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

dev.mysql.com/doc

github.com/OpenNMS/newts/wiki

Developer

DragonflyDB team and community contributors

Softmotions

Oracle

since 2010, originally MySQL AB, then Sun

OpenNMS Group

Initial release

2023

2012

1995

2014

Current release

1.0, March 2023

8.4.0, April 2024

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

GPLv2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C and C++

Java

Server operating systems

Linux

server-less

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

scheme-free

schema-free

yes

schema-free

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

with proprietary extensions

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

in-process shared library

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
Java 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

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java

Server-side scripts

Stored procedures

Lua

yes

proprietary syntax

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication
Source-replica replication

selectable replication factor

based on Cassandra

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic execution of command blocks and scripts

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

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

no user groups or roles

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.