DBMS > Apache Phoenix vs. InterSystems Caché vs. Redis vs. RisingWave

System Properties Comparison Apache Phoenix vs. InterSystems Caché vs. Redis vs. RisingWave

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

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 distributed RDBMS for stream processing, wire-compatible with PostgreSQL

Primary database model

Relational DBMS

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

Relational 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	2.06
Rank	#123	Overall
	#58	Relational DBMS

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

Score	0.64
Rank	#238	Overall
	#110	Relational DBMS

Website

phoenix.apache.org

www.intersystems.com/products/cache

redis.com
redis.io

www.risingwave.com/database

Technical documentation

phoenix.apache.org

docs.intersystems.com

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

docs.risingwave.com/docs/current/intro

Developer

Apache Software Foundation

InterSystems

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

RisingWave Labs

Initial release

2014

1997

2009

2022

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

2018.1.4, May 2020

7.2.5, May 2024

1.2, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

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

Java

Rust

Server operating systems

Linux
Unix
Windows

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

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Docker
Linux
macOS

Data scheme

yes

late-bound, schema-on-read capabilities

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

Standard SQL-types and JSON

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

with RediSQL module

yes

APIs and other access methods

JDBC

.NET Client API
JDBC
ODBC
RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

JDBC
PostgreSQL wire protocol

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
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

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

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

UDFs in Python or Java

Triggers

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

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

Hadoop integration

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or 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

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

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

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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

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.