DBMS > BigchainDB vs. Geode vs. HBase vs. IBM Cloudant vs. Redis

System Properties Comparison BigchainDB vs. Geode vs. HBase vs. IBM Cloudant vs. Redis

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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

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

Database as a Service offering based on Apache CouchDB

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

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.79
Rank	#212	Overall
	#36	Document stores

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

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

Website

www.bigchaindb.com

geode.apache.org

hbase.apache.org

www.ibm.com/products/cloudant

redis.com
redis.io

Technical documentation

bigchaindb.readthedocs.io/en/latest

geode.apache.org/docs

hbase.apache.org/book.html

cloud.ibm.com/docs/Cloudant

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

Developer

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

Apache Software Foundation

Apache top-level project, originally developed by Powerset

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2016

2002

2008

2010

2009

Current release

1.1, February 2017

2.3.4, January 2021

7.2.4, January 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache version 2

commercial

Open Source

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

Cloud-based only

Only available as a cloud service

yes

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

Python

Java

Erlang

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux
Unix
Windows

using Cygwin

hosted

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

schema-free

schema-free, schema definition possible

schema-free

Typing

predefined data types such as float or date

yes

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

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

SQL

Support of SQL

SQL-like query language (OQL)

with RediSQL module

APIs and other access methods

CLI Client
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

Java API
RESTful HTTP API
Thrift

RESTful HTTP/JSON API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

C
C#
C++
Groovy
Java
PHP
Python
Scala

C#
Java
JavaScript
Objective-C
PHP
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

Server-side scripts

Stored procedures

user defined functions

yes

Coprocessors in Java

View functions (Map-Reduce) in JavaScript

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

Triggers

yes

Cache Event Listeners

yes

publish/subscribe channels provide some trigger functionality; RedisGears

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

selectable replication factor

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

yes

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency

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

Transaction concepts

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

yes, on a single node

Single row ACID (across millions of columns)

atomic operations within a document possible

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

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

yes

Access rights per client and object definable

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

Access rights for users can be defined per database

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.