DBMS > BigObject vs. Redis vs. Warp 10

System Properties Comparison BigObject vs. Redis vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

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.

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Key-value store

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

Time Series 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.13
Rank	#342	Overall
	#150	Relational DBMS

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

Score	0.08
Rank	#358	Overall
	#35	Time Series DBMS

Website

bigobject.io

redis.com
redis.io

www.warp10.io

Technical documentation

docs.bigobject.io

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

www.warp10.io/content/02_Getting_started

Developer

BigObject, Inc.

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

SenX

Initial release

2015

2009

2015

Current release

7.2.4, January 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

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

Open Source

Apache License 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

Java

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

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 DML and DDL statements

with RediSQL module

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

HTTP API
Jupyter
WebSocket

Supported programming languages

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

Lua

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

yes

WarpScript

Triggers

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

Transaction concepts

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

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.