DBMS > Microsoft Azure Data Explorer vs. OpenSearch vs. Redis

System Properties Comparison Microsoft Azure Data Explorer vs. OpenSearch vs. Redis

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fully managed big data interactive analytics platform

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

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

Relational DBMS

column oriented

Search engine

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

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

Vector DBMS

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	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

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

Website

azure.microsoft.com/services/data-explorer

github.com/opensearch-project
opensearch.org

redis.com
redis.io

Technical documentation

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

opensearch.org/docs/latest

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

Developer

Microsoft

Amazon Web Services

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2019

2021

2009

Current release

cloud service with continuous releases

2.5.0, January 2023

7.2.4, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 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 OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Aiven for Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

Java

Server operating systems

hosted

All OS with a Java VM

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

Fixed schema with schema-less datatypes (dynamic)

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

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

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

all fields are automatically indexed

yes

All search fields are automatically indexed

yes

with RediSearch module

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

SQL-like query language

with RediSQL module

APIs and other access methods

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

Java API
RESTful HTTP/JSON API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

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

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

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, possible languages: KQL, Python, R

yes

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

Triggers

yes

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

yes

by using the 'percolation' feature

publish/subscribe channels provide some trigger functionality; RedisGears

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

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

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

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

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

Transaction concepts

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

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

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

User concepts

Access control

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

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.