DBMS > Microsoft Azure Data Explorer vs. Oracle vs. Redis vs. Sphinx

System Properties Comparison Microsoft Azure Data Explorer vs. Oracle vs. Redis vs. Sphinx

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

Widely used RDBMS

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.

Open source search engine for searching in data from different sources, e.g. relational databases

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

Search engine

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
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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	5.16
Rank	#69	Overall
	#37	Relational DBMS

Score	1234.27
Rank	#1	Overall
	#1	Relational DBMS

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

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

azure.microsoft.com/services/data-explorer

www.oracle.com/database

redis.com
redis.io

sphinxsearch.com

Technical documentation

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

docs.oracle.com/en/database

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

sphinxsearch.com/docs

Developer

Microsoft

Oracle

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Sphinx Technologies Inc.

Initial release

2019

1980

2009

2001

Current release

cloud service with continuous releases

23c, September 2023

7.2.4, January 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

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

Open Source

GPL version 2, commercial licence available

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 and C++

C++

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

Fixed schema with schema-less datatypes (dynamic)

yes

Schemaless in JSON and XML columns

schema-free

yes

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

with RediSearch module

yes

full-text index on all search fields

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

with RediSQL module

SQL-like query language (SphinxQL)

APIs and other access methods

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

proprietary protocol

RESP - REdis Serialization Protocol

Proprietary protocol

Supported programming languages

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

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++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

Yes, possible languages: KQL, Python, R

PL/SQL

also stored procedures in Java possible

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

Triggers

yes

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

yes

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, horizontal partitioning

Sharding

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

Sharding

Partitioning is done manually, search queries against distributed index is supported

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.

Multi-source replication
Source-replica replication

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

can be realized in PL/SQL

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

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

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

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

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

Azure Active Directory Authentication

fine grained access rights according to SQL-standard

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.