DBMS > BigchainDB vs. ClickHouse vs. OrigoDB vs. Redis vs. SAP SQL Anywhere

System Properties Comparison BigchainDB vs. ClickHouse vs. OrigoDB vs. Redis vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

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

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

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.

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Document store

Relational DBMS

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

Relational DBMS

Secondary database models

Time Series DBMS

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.85
Rank	#208	Overall
	#35	Document stores

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

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

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

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Website

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

bigchaindb.readthedocs.io/en/latest

clickhouse.com/docs

origodb.com/docs

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

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Clickhouse Inc.

Robert Friberg et al

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

SAP

formerly Sybase

Initial release

2016

2009

under the name LiveDB

2009

1992

Current release

v24.4.1.2088-stable, May 2024

7.2.5, May 2024

17, July 2015

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache 2.0

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.

Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.

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

Implementation language

Python

C++

Server operating systems

Linux

FreeBSD
Linux
macOS

Linux
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

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

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.

can be achieved using .NET

yes

Secondary indexes

yes

with RediSearch module

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

with RediSQL module

yes

APIs and other access methods

CLI Client
RESTful HTTP API

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

.NET Client API
HTTP API
LINQ

proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

.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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

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

yes, in C/C++, Java, .Net or Perl

Triggers

yes

Domain Events

publish/subscribe channels provide some trigger functionality; RedisGears

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

key based and custom

horizontal partitioning

client side managed; servers are not synchronized

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

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

Source-replica replication

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Source-replica replication

Database mirroring

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

Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

Write ahead log

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

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

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

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.