DBMS > KeyDB vs. Microsoft Azure Data Explorer vs. Redis vs. Teradata vs. Trafodion

System Properties Comparison KeyDB vs. Microsoft Azure Data Explorer vs. Redis vs. Teradata vs. Trafodion

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Fully managed big data interactive analytics 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.

A hybrid cloud data analytics software platform (Teradata Vantage)

Transactional SQL-on-Hadoop DBMS

Primary database model

Key-value store

Relational DBMS

column oriented

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

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

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.63
Rank	#232	Overall
	#32	Key-value stores

Score	3.28
Rank	#83	Overall
	#45	Relational DBMS

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

Score	41.47
Rank	#22	Overall
	#15	Relational DBMS

Website

github.com/Snapchat/KeyDB
keydb.dev

azure.microsoft.com/services/data-explorer

redis.com
redis.io

www.teradata.com

trafodion.apache.org

Technical documentation

docs.keydb.dev

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

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

docs.teradata.com

trafodion.apache.org/documentation.html

Developer

EQ Alpha Technology Ltd.

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Teradata

Apache Software Foundation, originally developed by HP

Initial release

2019

2009

1984

2014

Current release

cloud service with continuous releases

7.2.5, May 2024

Teradata Vantage 1.0 MU2, January 2019

2.3.0, February 2019

License

Commercial or Open Source

Open Source

BSD-3

commercial

Open Source

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

commercial

Open Source

Apache 2.0

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.

Implementation language

C++

C++, Java

Server operating systems

Linux

hosted

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

hosted
Linux

Linux

Data scheme

schema-free

Fixed schema with schema-less datatypes (dynamic)

schema-free

yes

Typing

predefined data types such as float or date

partial

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

yes

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

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.

yes

Secondary indexes

yes

by using the Redis Search module

all fields are automatically indexed

yes

with RediSearch module

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

yes

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

with RediSQL module

yes

SQL 2016 + extensions

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

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

proprietary protocol

RESP - REdis Serialization Protocol

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

ADO.NET
JDBC
ODBC

Supported programming languages

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

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

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Lua

Yes, possible languages: KQL, Python, R

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

yes

UDFs, stored procedures, table functions in parallel

Java Stored Procedures

Triggers

yes

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

publish/subscribe channels provide some trigger functionality; RedisGears

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

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

Sharding

Hashing

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

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

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Multi-source replication
Source-replica replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

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

through RedisGears

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong eventual consistency with CRDTs

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

Atomic execution of command blocks and scripts and optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

User concepts

Access control

simple password-based access control and ACL

Azure Active Directory Authentication

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

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.