DBMS > Dragonfly vs. EsgynDB vs. RavenDB vs. ToroDB

System Properties Comparison Dragonfly vs. EsgynDB vs. RavenDB vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Open Source Operational and Transactional Enterprise NoSQL Document Database

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Key-value store

Relational DBMS

Document store

Secondary database models

Graph DBMS
Spatial DBMS
Time Series 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.16
Rank	#329	Overall
	#146	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

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

www.esgyn.cn

ravendb.net

github.com/torodb/server

Technical documentation

www.dragonflydb.io/docs

ravendb.net/docs

Developer

DragonflyDB team and community contributors

Esgyn

Hibernating Rhinos

8Kdata

Initial release

2023

2015

2010

2016

Current release

1.0, March 2023

5.4, July 2022

License

Commercial or Open Source

Open Source

BSL 1.1

commercial

Open Source

AGPL version 3, commercial license available

Open Source

AGPL-V3

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

C++

C++, Java

Java

Server operating systems

Linux

Linux
macOS
Raspberry Pi
Windows

All OS with a Java 7 VM

Data scheme

scheme-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, boolean, date, object_id

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

yes

SQL

Support of SQL

yes

SQL-like query language (RQL)

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
JDBC
ODBC

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
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

All languages supporting JDBC/ODBC/ADO.Net

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

Lua

Java Stored Procedures

yes

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication between multi datacenters

Multi-source replication

Source-replica replication

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

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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

ACID, Cluster-wide transaction available

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

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

Access rights for users and 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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

DragonflyDB Announces $21m in New Funding and General Availability
21 March 2023, Business Wire

DragonflyDB reels in $21M for its speedy in-memory database
21 March 2023, SiliconANGLE News

Intel Linux Kernel Optimizations Show Huge Benefit For High Core Count Servers
29 March 2023, Phoronix

New Kubernetes Operator for Dragonfly In-Memory Datastore Now Available for Simplified Operations and Increased ...
18 April 2023, Business Wire

SFU Computing Science researchers receive 2022 ACM SIGMOD Research Highlight Award.
24 February 2023, Simon Fraser University News

provided by Google News

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and ...
13 June 2023, PR Newswire

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

Oren Eini on RavenDB, Including Consistency Guarantees and C# as the Implementation Language
23 May 2022, InfoQ.com

RavenDB Adds Graph Queries
15 May 2019, Datanami

How I Created a RavenDB Python Client
23 September 2016, Visual Studio Magazine

provided by Google News

Share this page