DBMS > Heroic vs. Redis vs. searchxml vs. Teradata

System Properties Comparison Heroic vs. Redis vs. searchxml vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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.

DBMS for structured and unstructured content wrapped with an application server

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Time Series DBMS

Key-value store

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

Native XML DBMS
Search engine

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

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

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

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Website

github.com/spotify/heroic

redis.com
redis.io

www.searchxml.net/category/products

www.teradata.com

Technical documentation

spotify.github.io/heroic

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

www.searchxml.net/support/handouts

docs.teradata.com

Developer

Spotify

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

informationpartners gmbh

Teradata

Initial release

2014

2009

2015

1984

Current release

7.2.4, January 2024

1.0

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

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

Implementation language

Java

C++

Server operating systems

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Windows

hosted
Linux

Data scheme

schema-free

yes

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

with RediSearch module

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

with RediSQL module

yes

SQL 2016 + extensions

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

RESTful HTTP API
WebDAV
XQuery
XSLT

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

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

C++

most other programming languages supported via APIs

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

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

yes

on the application server

yes

UDFs, stored procedures, table functions in parallel

Triggers

publish/subscribe channels provide some trigger functionality; RedisGears

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

yes

sychronisation to multiple collections

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

Transaction concepts

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

Atomic execution of command blocks and scripts and optimistic locking

multiple readers, single writer

ACID

Concurrency

Support for concurrent manipulation of data

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

Domain, group and role-based access control at the document level and for application services

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.