DBMS > BigchainDB vs. Blazegraph vs. Redis vs. Trafodion

System Properties Comparison BigchainDB vs. Blazegraph vs. Redis vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

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.

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store

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

Score	0.77
Rank	#222	Overall
	#20	Graph DBMS
	#8	RDF stores

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

Website

Technical documentation

bigchaindb.readthedocs.io/en/latest

wiki.blazegraph.com

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

trafodion.apache.org/documentation.html

Developer

Blazegraph

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Apache Software Foundation, originally developed by HP

Initial release

2016

2006

2009

2014

Current release

2.1.5, March 2019

7.2.4, January 2024

2.3.0, February 2019

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

extended commercial license 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

Java

C++, Java

Server operating systems

Linux

Linux
OS X
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

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

yes

SQL

Support of SQL

SPARQL is used as query language

with RediSQL module

yes

APIs and other access methods

CLI Client
RESTful HTTP API

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
C++
Java
JavaScript
PHP
Python
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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

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

Java Stored Procedures

Triggers

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in Graphs

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

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

yes

Security and Authentication via Web Application Container (Tomcat, Jetty)

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.