DBMS > HyperSQL vs. Neo4j vs. RavenDB vs. Redis vs. SingleStore

System Properties Comparison HyperSQL vs. Neo4j vs. RavenDB vs. Redis vs. SingleStore

Editorial information provided by DB-Engines

Name

Description

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Primary database model

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	3.49
Rank	#87	Overall
	#47	Relational DBMS

Score	44.46
Rank	#23	Overall
	#1	Graph DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	157.80
Rank	#6	Overall
	#1	Key-value stores

Score	5.60
Rank	#62	Overall
	#35	Relational DBMS

Website

Technical documentation

hsqldb.org/web/hsqlDocsFrame.html

neo4j.com/docs

ravendb.net/docs

docs.redis.com/latest/index.html
redis.io/docs

docs.singlestore.com

Developer

Neo4j, Inc.

Hibernating Rhinos

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

SingleStore Inc.

Initial release

2001

2007

2010

2009

2013

Current release

2.7.2, June 2023

5.19, April 2024

5.4, July 2022

7.2.4, January 2024

8.5, January 2024

License

Commercial or Open Source

Open Source

based on BSD license

Open Source

GPL version3, commercial licenses available

Open Source

AGPL version 3, commercial license available

Open Source

source-available extensions (modules), commercial licenses for Redis Enterprise

commercial

free developer edition available

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.

Neo4j Aura: Neo4j’s fully managed cloud service: The zero-admin, always-on graph database for cloud developers.

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

SingleStoreDB Cloud: The world's fastest, modern cloud database for both operational (OLTP) and analytical (OLAP) workloads. Available instantly with multi-cloud and hybrid-cloud capabilities

Implementation language

Java

Java, Scala

C++, Go

Server operating systems

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

Linux

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

Linux
macOS
Raspberry Pi
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

64 bit version required

Data scheme

yes

schema-free and schema-optional

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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.

Secondary indexes

yes

pluggable indexing subsystem, by default Apache Lucene

yes

with RediSearch module

yes

SQL

Support of SQL

yes

SQL-like query language (RQL)

with RediSQL module

yes

but no triggers and foreign keys

APIs and other access methods

HTTP API

JDBC via HTTP
JDBC
ODBC

Bolt protocol
Cypher query language
Java API
Neo4j-OGM

Object Graph Mapper
RESTful HTTP API
Spring Data Neo4j
TinkerPop 3

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Supported programming languages

All languages supporting JDBC/ODBC
Java

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

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

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Bash
C
C#
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java, SQL

yes

User defined Procedures and Functions

yes

Lua; Redis Functions coming in Redis 7 (slides and Github)

yes

Triggers

yes

via event handler

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

none

yes using Neo4j Fabric

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

Sharding

hash partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Causal Clustering using Raft protocol

available in in Enterprise Version only

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Source-replica replication

stores two copies of each physical data partition on two separate nodes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

through RedisGears

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

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
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

Atomic execution of command blocks and scripts and optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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

Authorization levels configured per client per database

Access Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based authentication

Fine grained access control via users, groups and roles

More information provided by the system vendor

Specific characteristics

Neo4j delivers graph technology that has been battle tested for performance and scale...
» more

SingleStore offers a fully-managed , distributed, highly-scalable SQL database designed...
» more

Competitive advantages

Neo4j is the market leader, graph database category creator, and the most widely...
» more

SingleStore’s competitive advantages include: Easy and Simplified Architecture with...
» more

Typical application scenarios

Real-Time Recommendations Master Data Management Identity and Access Management Network...
» more

Driving Fast Analytics: SingleStore delivers the fastest and most scalable reporting...
» more

Key customers

Over 800 commercial customers and over 4300 startups use Neo4j. Flagship customers...
» more

IEX Cloud : Improves Financial Data Distribution Speed 15x with Singlestore DB Comcast,...
» more

Market metrics

Neo4j boasts the world's largest graph database ecosystem with more than 140 million...
» more

Customers in various industries worldwide including US and International Industry...
» more

Licensing and pricing models

GPL v3 license that can be used all the places where you might use MySQL. Neo4j Commercial...
» more

F ree Tier and Enterprise Edition
» more

News

This Week in Neo4j: GraphRAG, Testcontainers, Metadata Management, App Dev and more
11 May 2024

Creating the GQL Database Language Standard
7 May 2024

This Week in Neo4j: GraphRAG, Knowledge Graphs, Open Source AI, GraphQL and more
4 May 2024

This Week in Neo4j: Nodes 2024, Data Modelling, Events, Knowledge Graphs and more
27 April 2024

GQL is Here: Your Cypher Queries in a GQL World
26 April 2024

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.