DBMS > Drizzle vs. Geode vs. InterSystems Caché vs. Redis vs. TigerGraph

System Properties Comparison Drizzle vs. Geode vs. InterSystems Caché vs. Redis vs. TigerGraph

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

A multi-model DBMS and application server

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 complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Relational DBMS

Key-value store

Key-value store
Object oriented DBMS
Relational DBMS

Key-value store

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

Graph 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	1.86
Rank	#134	Overall
	#24	Key-value stores

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

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

geode.apache.org

www.intersystems.com/products/cache

redis.com
redis.io

www.tigergraph.com

Technical documentation

geode.apache.org/docs

docs.intersystems.com

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

docs.tigergraph.com

Developer

Drizzle project, originally started by Brian Aker

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

InterSystems

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2008

2002

1997

2009

2017

Current release

7.2.4, September 2012

1.1, February 2017

2018.1.4, May 2020

7.2.5, May 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

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

commercial

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

C++

Java

C++

Server operating systems

FreeBSD
Linux
OS X

All OS with a Java VM

the JDK (8 or later) is also required

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

Data scheme

yes

schema-free

depending on used data model

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

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (OQL)

yes

with RediSQL module

SQL-like query language (GSQL)

APIs and other access methods

JDBC

Java Client API
Memcached protocol
RESTful HTTP API

.NET Client API
JDBC
ODBC
RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

C
C++
Java
PHP

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

C#
C++
Java

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

C++
Java

Server-side scripts

Stored procedures

user defined functions

yes

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

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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
Source-replica replication

Multi-source replication

Source-replica replication

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

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

Foreign keys

Referential integrity

yes

Relationships in graphs

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

ACID

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

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights per client and object definable

Access rights for users, groups and roles

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

Role-based access control

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.