DBMS > Apache Impala vs. Coveo vs. Datomic vs. JanusGraph vs. Redis

System Properties Comparison Apache Impala vs. Coveo vs. Datomic vs. JanusGraph vs. Redis

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

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

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

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.

Primary database model

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

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

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

Website

Technical documentation

impala.apache.org/impala-docs.html

docs.coveo.com

docs.datomic.com

docs.janusgraph.org

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

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Coveo

Cognitect

Linux Foundation; originally developed as Titan by Aurelius

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2013

2012

2017

2009

Current release

4.1.0, June 2022

1.0.6735, June 2023

0.6.3, February 2023

7.2.5, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

limited edition free

Open Source

Apache 2.0

Open Source

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

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

Java

Server operating systems

Linux

hosted

All OS with a Java VM

Linux
OS X
Unix
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

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

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

JDBC
ODBC

RESTful HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Python

Clojure
Java

Clojure
Java
Python

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

yes

user defined functions and integration of map-reduce

yes

Transaction Functions

yes

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

Triggers

yes

By using transaction functions

yes

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

But extensive use of caching in the application peers

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

none

But extensive use of caching in the application peers

yes

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

via Faunus, a graph analytics engine

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

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

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

yes

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

Durability

Support for making data persistent

yes

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

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

granular access controls, API key management, content filters

User authentification and security via Rexster Graph Server

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.