DBMS > Adabas vs. EventStoreDB vs. Greenplum vs. Neo4j vs. Redis

System Properties Comparison Adabas vs. EventStoreDB vs. Greenplum vs. Neo4j vs. Redis

Editorial information provided by DB-Engines

Name

Description

OLTP - DBMS for mainframes and Linux/Unix/Windows environments

used typically together with the Natural programming platform

Industrial-strength, open-source database solution built from the ground up for event sourcing.

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

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

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.

Primary database model

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

Secondary database models

Document store
Spatial DBMS

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	1.10
Rank	#179	Overall
	#1	Event Stores

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	44.46
Rank	#23	Overall
	#1	Graph DBMS

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

Website

www.softwareag.com/en_corporate/platform/adabas-natural.html

Technical documentation

developers.eventstore.com

docs.greenplum.org

neo4j.com/docs

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

Developer

Software AG

Event Store Limited

Pivotal Software Inc.

Neo4j, Inc.

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

1971

2012

2005

2007

2009

Current release

21.2, February 2021

7.0.0, September 2023

5.19, April 2024

7.2.4, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL version3, commercial licenses available

Open Source

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

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.

Implementation language

Java, Scala

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
Windows

Linux

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

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

schema-free and schema-optional

schema-free

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

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

since Version 4.2

Secondary indexes

yes

pluggable indexing subsystem, by default Apache Lucene

yes

with RediSearch module

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

with RediSQL module

APIs and other access methods

HTTP API

with add-on software Adabas SOA Gateway
SOAP-based API

with add-on software Adabas SOA Gateway

JDBC
ODBC

Bolt protocol
Cypher query language
Java API
Neo4j-OGM

Object Graph Mapper
RESTful HTTP API
Spring Data Neo4j
TinkerPop 3

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

Natural

C
Java
Perl
Python
R

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

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

Server-side scripts

Stored procedures

in Natural

yes

User defined Procedures and Functions

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

Triggers

yes

via event handler

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

yes, with additonal products like Adabas Cluster Services, Adabas Parallel Services, Adabas Vista

Sharding

yes using Neo4j Fabric

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Source-replica replication

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

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

through RedisGears

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

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

In-memory capabilities

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

yes

User concepts

Access control

only with OS-specific tools (e.g. IBM RACF, CA Top Secret)

fine grained access rights according to SQL-standard

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

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

More information provided by the system vendor

Specific characteristics

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

Competitive advantages

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

Typical application scenarios

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

Key customers

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

Market metrics

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

Licensing and pricing models

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

News

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

GQL: The ISO Standard for Graphs Has Arrived
25 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.