DBMS > Geode vs. MarkLogic vs. Redis vs. Riak KV vs. SWC-DB

System Properties Comparison Geode vs. MarkLogic vs. Redis vs. Riak KV vs. SWC-DB

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

Operational and transactional Enterprise NoSQL 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.

Distributed, fault tolerant key-value store

A high performance, scalable Wide Column DBMS

Primary database model

Key-value store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Key-value store

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

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Wide column store

Secondary database models

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Time Series DBMS

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

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

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

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

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

geode.apache.org

www.marklogic.com

redis.com
redis.io

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

geode.apache.org/docs

docs.marklogic.com

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

www.tiot.jp/riak-docs/riak/kv/latest

Developer

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

MarkLogic Corp.

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

OpenSource, formerly Basho Technologies

Alex Kashirin

Initial release

2002

2001

2009

2020

Current release

1.1, February 2017

11.0, December 2022

7.2.4, January 2024

3.2.0, December 2022

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

restricted free version is available

Open Source

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

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPL V3

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

C++

Erlang

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
OS X

Linux

Data scheme

schema-free

Schema can be enforced

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

Secondary indexes

yes

with RediSearch module

restricted

SQL

Support of SQL

SQL-like query language (OQL)

yes

SQL92

with RediSQL module

SQL-like query language

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

proprietary protocol

RESP - REdis Serialization Protocol

HTTP API
Native Erlang Interface

Proprietary protocol
Thrift

Supported programming languages

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

C
C#
C++
Java
JavaScript (Node.js)
Perl
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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C++

Server-side scripts

Stored procedures

user defined functions

yes

via XQuery or JavaScript

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

Erlang

Triggers

yes

Cache Event Listeners

yes

publish/subscribe channels provide some trigger functionality; RedisGears

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

through RedisGears

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

yes, on a single node

ACID

can act as a resource manager in an XA/JTA transaction

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

yes, with Range Indexes

yes

User concepts

Access control

Access rights per client and object definable

Role-based access control at the document and subdocument levels

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

yes, using Riak Security

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.