DBMS > Apache Impala vs. Blueflood vs. Datomic vs. Redis vs. Vitess

System Properties Comparison Apache Impala vs. Blueflood vs. Datomic vs. Redis vs. Vitess

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Scalable TimeSeries DBMS based on Cassandra

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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.

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

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

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

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

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

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

Technical documentation

impala.apache.org/impala-docs.html

github.com/rax-maas/blueflood/wiki

docs.datomic.com

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

vitess.io/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Rackspace

Cognitect

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

The Linux Foundation, PlanetScale

Initial release

2013

2012

2009

2013

Current release

4.1.0, June 2022

1.0.6735, June 2023

7.2.4, January 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

commercial

limited edition free

Open Source

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

Open Source

Apache Version 2.0, commercial licenses available

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

C++

Java

Java, Clojure

Server operating systems

Linux

Linux
OS X

All OS with a Java VM

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Docker
Linux
macOS

Data scheme

yes

predefined 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

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

yes

SQL

Support of SQL

SQL-like DML and DDL statements

with RediSQL module

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

HTTP REST

RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

Transaction Functions

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

yes

proprietary syntax

Triggers

By using transaction functions

publish/subscribe channels provide some trigger functionality; RedisGears

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

But extensive use of caching in the application peers

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

But extensive use of caching in the application peers

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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 at shard level

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

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

recommended only for testing and development

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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

Users with fine-grained authorization concept

no user groups or roles

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.