DBMS > Apache Impala vs. Google Cloud Datastore vs. Redis vs. TimesTen vs. VoltDB

System Properties Comparison Apache Impala vs. Google Cloud Datastore vs. Redis vs. TimesTen vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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.

In-Memory RDBMS compatible to Oracle

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Document store

Key-value store

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

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

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

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

impala.apache.org

cloud.google.com/datastore

redis.com
redis.io

www.oracle.com/database/technologies/related/timesten.html

www.voltdb.com

Technical documentation

impala.apache.org/impala-docs.html

cloud.google.com/datastore/docs

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

docs.oracle.com/database/timesten-18.1

docs.voltdb.com

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Google

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

VoltDB Inc.

Initial release

2013

2008

2009

1998

2010

Current release

4.1.0, June 2022

7.2.5, May 2024

11 Release 2 (11.2.2.8.0)

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

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

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Cloud-based only

Only available as a cloud service

yes

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, C++

Server operating systems

Linux

hosted

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
OS X

for development

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

with RediSQL module

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

proprietary protocol

RESP - REdis Serialization Protocol

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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++
Java
PL/SQL

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

using Google App Engine

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

PL/SQL

Java

Triggers

Callbacks using the Google Apps Engine

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using Paxos

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

yes

using Google Cloud Dataflow

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

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

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Atomic execution of command blocks and scripts and optimistic locking

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

by means of logfiles and checkpoints

yes

Snapshots and command logging

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 based on Google Cloud Identity and Access Management (IAM)

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

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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.