DBMS > Graph Engine vs. MarkLogic vs. Oracle Rdb vs. Redis vs. Tigris

System Properties Comparison Graph Engine vs. MarkLogic vs. Oracle Rdb vs. Redis vs. Tigris

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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.

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Graph DBMS
Key-value store

Document store
Native XML DBMS
RDF store

as of version 7
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

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

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	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

Score	1.14
Rank	#178	Overall
	#80	Relational DBMS

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

Score	0.09
Rank	#363	Overall
	#49	Document stores
	#54	Key-value stores
	#22	Search engines
	#38	Time Series DBMS

Website

www.graphengine.io

www.progress.com/marklogic

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

redis.com
redis.io

www.tigrisdata.com

Technical documentation

www.graphengine.io/docs/manual

www.progress.com/marklogic/documentation

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

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

www.tigrisdata.com/docs

Developer

Microsoft

MarkLogic Corp.

Oracle, originally developed by Digital Equipment Corporation (DEC)

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Tigris Data, Inc.

Initial release

2010

2001

1984

2009

2022

Current release

11.0, December 2022

7.4.1.1, 2021

7.2.5, May 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

restricted free version is available

commercial

Open Source

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

Open Source

Apache Version 2.0

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

.NET and C

C++

Server operating systems

.NET

Linux
OS X
Windows

HP Open VMS

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
macOS
Windows

Data scheme

yes

schema-free

Schema can be enforced

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

schema-free

yes

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

yes

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

yes

SQL

Support of SQL

yes

SQL92

yes

with RediSQL module

APIs and other access methods

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

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

C#
C++
F#
Visual Basic

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

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

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

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

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

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes, using FoundationDB

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

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

Access rights for users and roles

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.