DBMS > Geode vs. GigaSpaces vs. IBM Db2 vs. Redis vs. RocksDB

System Properties Comparison Geode vs. GigaSpaces vs. IBM Db2 vs. Redis vs. RocksDB

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

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Common in IBM host environments, 2 different versions for host and Windows/Linux

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.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Key-value store

Document store
Object oriented DBMS

Values are user defined objects

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

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
Search engine

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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.86
Rank	#134	Overall
	#24	Key-value stores

Score	1.03
Rank	#188	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

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

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

geode.apache.org

www.gigaspaces.com

www.ibm.com/products/db2

redis.com
redis.io

rocksdb.org

Technical documentation

geode.apache.org/docs

docs.gigaspaces.com/latest/landing.html

www.ibm.com/docs/en/db2

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

github.com/facebook/rocksdb/wiki

Developer

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

Gigaspaces Technologies

IBM

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Facebook, Inc.

Initial release

2002

2000

1983

host version

2009

2013

Current release

1.1, February 2017

15.5, September 2020

12.1, October 2016

7.2.5, May 2024

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache Version 2; Commercial licenses available

commercial

free version is available

Open Source

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

Open Source

BSD

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

C and C++

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
macOS
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows
z/OS

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

Data scheme

schema-free

yes

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.

XML can be used for describing objects metadata

Secondary indexes

yes

with RediSearch module

SQL

Support of SQL

SQL-like query language (OQL)

SQL-99 for query and DML statements

yes

with RediSQL module

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

proprietary protocol

RESP - REdis Serialization Protocol

C++ API
Java API

Supported programming languages

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

.Net
C++
Java
Python
Scala

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

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
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

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

Triggers

yes

Cache Event Listeners

yes, event driven architecture

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

Sharding

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

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

yes

with separate tools (MQ, InfoSphere)

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

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

Transaction concepts

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

yes, on a single node

ACID

Atomic execution of command blocks and scripts and optimistic locking

yes

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

Role-based access control

fine grained access rights according to SQL-standard

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.