DBMS > Geode vs. MarkLogic vs. OpenSearch vs. Oracle Rdb vs. Redis

System Properties Comparison Geode vs. MarkLogic vs. OpenSearch vs. Oracle Rdb vs. Redis

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

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

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

Key-value store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Search engine

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

Vector 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.51
Rank	#147	Overall
	#25	Key-value stores

Score	4.15
Rank	#70	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#8	Search engines

Score	16.31
Rank	#36	Overall
	#4	Search engines

Score	1.04
Rank	#184	Overall
	#84	Relational DBMS

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

Website

geode.apache.org

www.progress.com/marklogic

github.com/opensearch-project
opensearch.org

www.oracle.com/database/technologies/related/rdb.html

redis.com
redis.io

Technical documentation

geode.apache.org/docs

www.progress.com/marklogic/documentation

opensearch.org/docs/latest

www.oracle.com/database/technologies/related/rdb-doc.html

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.

MarkLogic Corp.

Amazon Web Services

Oracle, originally developed by Digital Equipment Corporation (DEC)

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2002

2001

2021

1984

2009

Current release

1.1, February 2017

11.0, December 2022

2.5.0, January 2023

7.4.1.1, 2021

7.2.5, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

restricted free version is available

Open Source

Apache Version 2.0

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.

STACKIT OpenSearch offers OpenSearch in a managed version in enterprise grade, 100% GDPR-compliant, for a wide range of applications like analytics, website search, offering scalability and fast data access.

Implementation language

Java

C++

Java

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Windows

All OS with a Java VM

HP Open VMS

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

schema-free

Schema can be enforced

schema-free

Flexible type definitions. Once a type is defined, it is persistent

Flexible Schema (defined schema, partial schema, schema free)

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

All search fields are automatically indexed

yes

with RediSearch module

SQL

Support of SQL

SQL-like query language (OQL)

yes

SQL92

SQL-like query language

yes

with RediSQL module

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

Java API
RESTful HTTP/JSON API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

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

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

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

yes

via XQuery or JavaScript

yes

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

Triggers

yes

Cache Event Listeners

yes

by using the 'percolation' feature

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

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

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

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

yes, on a single node

ACID

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

yes, on a single node

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

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

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

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.