DBMS > Blueflood vs. HarperDB vs. Redis vs. SpaceTime

System Properties Comparison Blueflood vs. HarperDB vs. Redis vs. SpaceTime

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

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.

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Time Series DBMS

Document store

Key-value store

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Spatial 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

Relational DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	0.60
Rank	#244	Overall
	#38	Document stores

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

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Website

blueflood.io

www.harperdb.io

redis.com
redis.io

www.mireo.com/spacetime

Technical documentation

github.com/rax-maas/blueflood/wiki

docs.harperdb.io/docs

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

Developer

Rackspace

HarperDB

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Mireo

Initial release

2013

2017

2009

2020

Current release

3.1, August 2021

7.2.5, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free community edition available

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 Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

Java

Node.js

C++

Server operating systems

Linux
OS X

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

Data scheme

predefined scheme

dynamic schema

schema-free

yes

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

A subset of ANSI SQL is implemented

APIs and other access methods

HTTP REST

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

proprietary protocol

RESP - REdis Serialization Protocol

RESTful HTTP API

Supported programming languages

.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

C#
C++
Python

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

based on Cassandra

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

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

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

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

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

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

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

yes

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.