DBMS > Apache HBase vs. Redis vs. Valentina Server

System Properties Comparison Apache HBase vs. Redis vs. Valentina Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Wide-column store based on Apache Hadoop and on concepts of BigTable

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.

Object-relational database and reports server

Primary database model

Wide column store

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	27.41
Rank	#26	Overall
	#2	Wide column stores

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

Score	0.18
Rank	#313	Overall
	#140	Relational DBMS

Website

hbase.apache.org

redis.com
redis.io

www.valentina-db.net

Technical documentation

hbase.apache.org/book.html

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

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Paradigma Software

Initial release

2008

2009

1999

Current release

2.3.4, January 2021

7.2.5, May 2024

5.7.5

License

Commercial or Open Source

Open Source

Apache version 2

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.

Implementation language

Java

Server operating systems

Linux
Unix
Windows

using Cygwin

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
OS X
Windows

Data scheme

schema-free, schema definition possible

schema-free

yes

Typing

predefined data types such as float or date

options to bring your own types, AVRO

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.

Secondary indexes

yes

with RediSearch module

yes

SQL

Support of SQL

with RediSQL module

yes

APIs and other access methods

Java API
RESTful HTTP API
Thrift

proprietary protocol

RESP - REdis Serialization Protocol

ODBC

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

Coprocessors in Java

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

yes

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

yes

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
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

yes

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

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

Single row ACID (across millions of columns)

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 (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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

fine grained access rights according to SQL-standard

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.