DBMS > Dragonfly vs. Neo4j vs. OpenEdge

System Properties Comparison Dragonfly vs. Neo4j vs. OpenEdge

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

Scalable, ACID-compliant graph database designed with a high-performance distributed cluster architecture, available in self-hosted and cloud offerings

Application development environment with integrated database management system

Primary database model

Key-value store

Graph DBMS

Relational DBMS

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

Score	0.50
Rank	#243	Overall
	#35	Key-value stores

Score	46.15
Rank	#20	Overall
	#1	Graph DBMS

Score	3.48
Rank	#74	Overall
	#39	Relational DBMS

Website

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

neo4j.com

www.progress.com/openedge

Technical documentation

www.dragonflydb.io/docs

neo4j.com/docs

documentation.progress.com/output/ua/OpenEdge_latest

Developer

DragonflyDB team and community contributors

Neo4j, Inc.

Progress Software Corporation

Initial release

2023

2007

1984

Current release

1.0, March 2023

5.23, August 2024

OpenEdge 12.2, March 2020

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

GPL version3, commercial licenses available

commercial

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

Java, Scala

Server operating systems

Linux

Can also be used server-less as embedded Java database.
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

scheme-free

schema-free and schema-optional

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

pluggable indexing subsystem, by default Apache Lucene

yes

SQL

Support of SQL

yes

close to SQL 92

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

Bolt protocol
Cypher query language
Java API
Neo4j-OGM

Object Graph Mapper
RESTful HTTP API
Spring Data Neo4j
TinkerPop 3

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

.Net
Clojure
Elixir
Go
Groovy
Haskell
Java
JavaScript
Perl
PHP
Python
Ruby
Scala

Progress proprietary ABL (Advanced Business Language)

Server-side scripts

Stored procedures

Lua

yes

User defined Procedures and Functions

yes

Triggers

publish/subscribe channels provide some trigger functionality

yes

via event handler

yes

Partitioning methods

Methods for storing different data on different nodes

yes using Neo4j Fabric

horizontal partitioning

since Version 11.4

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Causal Clustering using Raft protocol

available in in Enterprise Version only

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Causal and Eventual Consistency configurable in Causal Cluster setup
Immediate Consistency in stand-alone mode

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

Users, roles and permissions. Pluggable authentication with supported standards (LDAP, Active Directory, Kerberos)

Users and groups

More information provided by the system vendor

News

This Week in Neo4j: Knowledge Graph, Deepseek, Bloodhound, RAG and more
15 March 2025

Graph Database vs. Relational Database: What’s The Difference?
13 March 2025

How to Build a Knowledge Graph in 7 Steps
12 March 2025

Function Calling in Agentic Workflows
12 March 2025

Automate Start and Stop of Neo4j AuraDB Instances Using GitHub Actions
11 March 2025

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

DB-Engines blog posts

Applying Graph Analytics to Game of Thrones
12 June 2019, Amy Hodler & Mark Needham, Neo4j (guest author)

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

The openCypher Project: Help Shape the SQL for Graphs
22 December 2015, Emil Eifrem (guest author)

show all

Share this page