DBMS > Amazon Neptune vs. Apache Drill vs. Apache Impala vs. Datomic vs. Redis

System Properties Comparison Amazon Neptune vs. Apache Drill vs. Apache Impala vs. Datomic vs. Redis

Editorial information provided by DB-Engines

Name

Description

Fast, reliable graph database built for the cloud

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Analytic DBMS for Hadoop

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.

Primary database model

Graph DBMS
RDF store

Document store
Relational DBMS

Relational DBMS

Key-value store

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	2.20
Rank	#119	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

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

Website

aws.amazon.com/neptune

Technical documentation

aws.amazon.com/neptune/developer-resources

drill.apache.org/docs

impala.apache.org/impala-docs.html

docs.datomic.com

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

Developer

Amazon

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Cognitect

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2017

2012

2013

2012

2009

Current release

1.20.3, January 2023

4.1.0, June 2022

1.0.6735, June 2023

7.2.4, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache Version 2

commercial

limited edition free

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

Server operating systems

hosted

Linux
OS X
Windows

Linux

All OS with a Java VM

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

schema-free

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 SELECT statement is SQL:2003 compliant

SQL-like DML and DDL statements

with RediSQL module

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

C++

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

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions and integration of map-reduce

yes

Transaction Functions

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

Triggers

By using transaction functions

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

But extensive use of caching in the application peers

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

selectable replication factor

none

But extensive use of caching in the application peers

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

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

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

with encyption-at-rest

Depending on the underlying data source

yes

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

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.

Depending on the underlying data source

yes

recommended only for testing and development

yes

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Depending on the underlying data source

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

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.