DBMS > Hive vs. Microsoft Azure Data Explorer vs. NuoDB vs. Redis vs. Tarantool

System Properties Comparison Hive vs. Microsoft Azure Data Explorer vs. NuoDB vs. Redis vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Fully managed big data interactive analytics platform

NuoDB is a webscale distributed database that supports SQL and ACID transactions

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 computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

column oriented

Relational DBMS

Key-value store

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

Document store
Key-value store
Relational DBMS

Secondary database models

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	0.89
Rank	#198	Overall
	#92	Relational DBMS

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

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

hive.apache.org

azure.microsoft.com/services/data-explorer

www.3ds.com/nuodb-distributed-sql-database

redis.com
redis.io

www.tarantool.io

Technical documentation

cwiki.apache.org/confluence/display/Hive/Home

docs.microsoft.com/en-us/azure/data-explorer

doc.nuodb.com

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

www.tarantool.io/en/doc

Developer

Apache Software Foundation

initially developed by Facebook

Microsoft

Dassault Systèmes

originally NuoDB, Inc.

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2012

2019

2013

2009

2008

Current release

3.1.3, April 2022

cloud service with continuous releases

7.2.5, May 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

limited edition free

Open Source

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

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool 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

Java

C++

C and C++

Server operating systems

All OS with a Java VM

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

BSD
Linux
macOS

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

string, double, decimal, uuid, integer, blob, boolean, datetime

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.

yes

Secondary indexes

yes

all fields are automatically indexed

yes

with RediSearch module

yes

SQL

Support of SQL

SQL-like DML and DDL statements

Kusto Query Language (KQL), SQL subset

yes

with RediSQL module

Full-featured ANSI SQL support

APIs and other access methods

JDBC
ODBC
Thrift

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

ADO.NET
JDBC
ODBC

proprietary protocol

RESP - REdis Serialization Protocol

Open binary protocol

Supported programming languages

C++
Java
PHP
Python

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

.Net
C
C++
Go
Java
JavaScript
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#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

Yes, possible languages: KQL, Python, R

Java, SQL

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

Lua, C and SQL stored procedures

Triggers

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

publish/subscribe channels provide some trigger functionality; RedisGears

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

data is dynamically stored/cached on the nodes where it is read/written

Sharding

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

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

Managed transparently by NuoDB

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Spark connector (open source): github.com/Azure/azure-kusto-spark

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate 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

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

tunable commit protocol

Atomic execution of command blocks and scripts and optimistic locking

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

Data access is serialized by the server

yes, cooperative multitasking

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Temporary table

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access rights for users, groups and roles

Azure Active Directory Authentication

Standard SQL roles/ privileges, Administrative Users

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

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and 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.