DBMS > Apache Impala vs. EXASOL vs. Redis vs. RRDtool

System Properties Comparison Apache Impala vs. EXASOL vs. Redis vs. RRDtool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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.

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Primary database model

Relational DBMS

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	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	1.66
Rank	#138	Overall
	#64	Relational DBMS

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

Score	1.70
Rank	#136	Overall
	#11	Time Series DBMS

Website

impala.apache.org

www.exasol.com

redis.com
redis.io

oss.oetiker.ch/rrdtool

Technical documentation

impala.apache.org/impala-docs.html

www.exasol.com/resources

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

oss.oetiker.ch/rrdtool/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Exasol

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Tobias Oetiker

Initial release

2013

2000

2009

1999

Current release

4.1.0, June 2022

7.2.5, May 2024

1.8.0, 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

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

Open Source

GPL V2 and FLOSS

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.

Implementation language

C++

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

Linux

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

HP-UX
Linux

Data scheme

yes

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

Numeric data only

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.

Exporting into and restoring from XML files possible

Secondary indexes

yes

with RediSearch module

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with RediSQL module

APIs and other access methods

JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

proprietary protocol

RESP - REdis Serialization Protocol

in-process shared library
Pipes

Supported programming languages

All languages supporting JDBC/ODBC

Java
Lua
Python
R

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

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

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

Triggers

yes

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Hadoop integration

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

none

Foreign keys

Referential integrity

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

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

by using the rrdcached daemon

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 rights for users, groups and roles

based on Apache Sentry and Kerberos

Access rights for users, groups and roles according to SQL-standard

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

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.