DBMS > BigchainDB vs. HarperDB vs. Redis vs. TinkerGraph

System Properties Comparison BigchainDB vs. HarperDB vs. Redis vs. TinkerGraph

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

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 lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Document store

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

Score	0.55
Rank	#252	Overall
	#38	Document stores

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

Score	0.12
Rank	#344	Overall
	#34	Graph DBMS

Website

www.bigchaindb.com

www.harperdb.io

redis.com
redis.io

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.harperdb.io/docs

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

Developer

HarperDB

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2016

2017

2009

Current release

3.1, August 2021

7.2.4, January 2024

License

Commercial or Open Source

Open Source

AGPL v3

commercial

free community edition available

Open Source

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

Open Source

Apache 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

Python

Node.js

Java

Server operating systems

Linux

Linux
OS X

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

schema-free

dynamic schema

schema-free

Typing

predefined data types such as float or date

yes

JSON data types

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

SQL

Support of SQL

SQL-like data manipulation statements

with RediSQL module

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

proprietary protocol

RESP - REdis Serialization Protocol

TinkerPop 3

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

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

Groovy
Java

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

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

Triggers

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

A table resides as a whole on one (or more) nodes in a cluster

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

the nodes on which a table resides can be defined

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

Atomic execution of specific operations

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,with MongoDB ord RethinkDB

yes, using LMDB

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

optional

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

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.