DBMS > Microsoft Azure Data Explorer vs. Redis vs. Spark SQL vs. Sphinx vs. Splice Machine

System Properties Comparison Microsoft Azure Data Explorer vs. Redis vs. Spark SQL vs. Sphinx vs. Splice Machine

Editorial information provided by DB-Engines

Name

Description

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.

Spark SQL is a component on top of 'Spark Core' for structured data processing

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

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

Search engine

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

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

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

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

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Website

azure.microsoft.com/services/data-explorer

Technical documentation

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

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

spark.apache.org/docs/latest/sql-programming-guide.html

sphinxsearch.com/docs

splicemachine.com/how-it-works

Developer

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Apache Software Foundation

Sphinx Technologies Inc.

Splice Machine

Initial release

2019

2009

2014

2001

2014

Current release

cloud service with continuous releases

7.2.5, May 2024

3.5.0 ( 2.13), September 2023

3.5.1, February 2023

3.1, March 2021

License

Commercial or Open Source

commercial

Open Source

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

Open Source

Apache 2.0

Open Source

GPL version 2, commercial licence available

Open Source

AGPL 3.0, commercial license 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

Scala

C++

Java

Server operating systems

hosted

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
OS X
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Data scheme

Fixed schema with schema-less datatypes (dynamic)

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

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

all fields are automatically indexed

yes

with RediSearch module

yes

full-text index on all search fields

yes

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

with RediSQL module

SQL-like DML and DDL statements

SQL-like query language (SphinxQL)

yes

APIs and other access methods

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

proprietary protocol

RESP - REdis Serialization Protocol

JDBC
ODBC

Proprietary protocol

JDBC
Native Spark Datasource
ODBC

Supported programming languages

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

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

Java
Python
R
Scala

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

Yes, possible languages: KQL, Python, R

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

yes

Java

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

yes, utilizing Spark Core

Sharding

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

Shared Nothhing Auto-Sharding, Columnar Partitioning

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

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

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

through RedisGears

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

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

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

yes, multi-version concurrency control (MVCC)

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.

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

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

Access rights for users, groups and roles 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.