DBMS > Geode vs. GridGain vs. RavenDB vs. Redis vs. STSdb

System Properties Comparison Geode vs. GridGain vs. RavenDB vs. Redis vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

GridGain is an in-memory computing platform, built on Apache Ignite

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.

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Key-value store

Key-value store
Relational DBMS

Document store

Key-value store

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

Key-value store

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

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

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

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

github.com/STSSoft/STSdb4

Technical documentation

geode.apache.org/docs

www.gridgain.com/docs/index.html

ravendb.net/docs

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

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

GridGain Systems, Inc.

Hibernating Rhinos

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

STS Soft SC

Initial release

2002

2007

2010

2009

2011

Current release

1.1, February 2017

GridGain 8.5.1

5.4, July 2022

7.2.4, January 2024

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

AGPL version 3, commercial license available

Open Source

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

Open Source

GPLv2, commercial license 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.

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

Implementation language

Java

Java, C++, .Net

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Windows

Data scheme

schema-free

yes

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

primitive types and user defined types (classes)

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

with RediSearch module

SQL

Support of SQL

SQL-like query language (OQL)

ANSI-99 for query and DML statements, subset of DDL

SQL-like query language (RQL)

with RediSQL module

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

.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

.NET Client API

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

C#
C++
Java
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

C#
Java

Server-side scripts

Stored procedures

user defined functions

yes (compute grid and cache interceptors can be used instead)

yes

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

Triggers

yes

Cache Event Listeners

yes (cache interceptors and events)

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes (replicated cache)

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

through RedisGears

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

Foreign keys

Referential integrity

Transaction concepts

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

yes, on a single node

ACID

ACID, Cluster-wide transaction available

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

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

Access rights per client and object definable

Security Hooks for custom implementations

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

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.