DBMS > Graph Engine vs. HBase vs. OrigoDB vs. Redis

System Properties Comparison Graph Engine vs. HBase vs. OrigoDB vs. Redis

Please select another system to include it in the comparison.

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

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

A fully ACID in-memory object graph 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.

Primary database model

Graph DBMS
Key-value store

Wide column store

Document store
Object oriented 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

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

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

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

Website

Technical documentation

www.graphengine.io/docs/manual

hbase.apache.org/book.html

origodb.com/docs

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

Developer

Microsoft

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Robert Friberg et al

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2010

2008

2009

under the name LiveDB

2009

Current release

2.3.4, January 2021

7.2.5, May 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache version 2

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.

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

.NET and C

Java

Server operating systems

.NET

Linux
Unix
Windows

using Cygwin

Linux
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

schema-free, schema definition possible

yes

schema-free

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

with RediSearch module

SQL

Support of SQL

with RediSQL module

APIs and other access methods

RESTful HTTP API

Java API
RESTful HTTP API
Thrift

.NET Client API
HTTP API
LINQ

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

C#
C++
F#
Visual Basic

C
C#
C++
Groovy
Java
PHP
Python
Scala

.Net

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

yes

Coprocessors in Java

yes

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

Triggers

yes

Domain Events

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

horizontal partitioning

client side managed; servers are not synchronized

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

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

depending on model

Transaction concepts

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

Single row ACID (across millions of columns)

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

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

yes

Write ahead log

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

User concepts

Access control

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Role based authorization

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

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.