DBMS > Datomic vs. Geode vs. Immudb vs. Redis

System Properties Comparison Datomic vs. Geode vs. Immudb vs. Redis

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

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

Relational DBMS

Key-value store

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

Secondary database models

Relational 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.55
Rank	#144	Overall
	#67	Relational DBMS

Score	1.51
Rank	#147	Overall
	#25	Key-value stores

Score	0.24
Rank	#295	Overall
	#42	Key-value stores

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

Website

www.datomic.com

geode.apache.org

github.com/codenotary/immudb
immudb.io

redis.com
redis.io

Technical documentation

docs.datomic.com

geode.apache.org/docs

docs.immudb.io

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

Developer

Cognitect

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

Codenotary

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2012

2002

2020

2009

Current release

1.0.7180, July 2024

1.1, February 2017

1.2.3, April 2022

7.2.5, May 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache Version 2.0

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.

Implementation language

Java, Clojure

Java

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

BSD
Linux
macOS
Solaris
Windows
z/OS

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

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.

Secondary indexes

yes

with RediSearch module

SQL

Support of SQL

SQL-like query language (OQL)

SQL-like syntax

with RediSQL module

APIs and other access methods

RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

gRPC protocol
PostgreSQL wire protocol

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

Clojure
Java

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

.Net
Go
Java
JavaScript (Node.js)
Python

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

yes

Transaction Functions

user defined functions

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

Triggers

By using transaction functions

yes

Cache Event Listeners

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

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

ACID

yes, on a single node

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

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

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

recommended only for testing and development

yes

User concepts

Access control

Access rights per client and object definable

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.