DBMS > Citus vs. Datomic vs. GigaSpaces vs. GridGain vs. Redis

System Properties Comparison Citus vs. Datomic vs. GigaSpaces vs. GridGain vs. Redis

Editorial information provided by DB-Engines

Name

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

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

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

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

Document store
Object oriented DBMS

Values are user defined objects

Key-value store
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

Document store

Graph DBMS
Search engine

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	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

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

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

Website

Technical documentation

docs.citusdata.com

docs.datomic.com

docs.gigaspaces.com/latest/landing.html

www.gridgain.com/docs/index.html

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

Developer

Cognitect

Gigaspaces Technologies

GridGain Systems, Inc.

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2010

2012

2000

2007

2009

Current release

8.1, December 2018

1.0.6735, June 2023

15.5, September 2020

GridGain 8.5.1

7.2.4, January 2024

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

commercial

limited edition free

Open Source

Apache Version 2; Commercial licenses available

commercial

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.

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

Implementation language

Java, Clojure

Java, C++, .Net

Server operating systems

Linux

All OS with a Java VM

Linux
macOS
Solaris
Windows

Linux
OS X
Solaris
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

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.

yes

specific XML type available, but no XML query functionality

XML can be used for describing objects metadata

yes

Secondary indexes

yes

with RediSearch module

SQL

Support of SQL

yes

standard, with numerous extensions

SQL-99 for query and DML statements

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

with RediSQL module

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP API

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

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

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Clojure
Java

.Net
C++
Java
Python
Scala

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

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

Transaction Functions

yes

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

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

Triggers

yes

By using transaction functions

yes, event driven architecture

yes (cache interceptors and events)

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Source-replica replication

other methods possible by using 3rd party extensions

none

But extensive use of caching in the application peers

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

yes (replicated cache)

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

Map-Reduce pattern can be built with XAP task executors

yes (compute grid and hadoop accelerator)

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

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

yes

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

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

fine grained access rights according to SQL-standard

Role-based access control

Security Hooks for custom implementations

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.