DBMS > Heroic vs. Microsoft Azure Data Explorer vs. Prometheus vs. Redis vs. SAP Advantage Database Server

System Properties Comparison Heroic vs. Microsoft Azure Data Explorer vs. Prometheus vs. Redis vs. SAP Advantage Database Server

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Fully managed big data interactive analytics platform

Open-source Time Series DBMS and monitoring system

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.

Low-cost RDBMS with access to ISAM and FoxPro data structures

Primary database model

column oriented

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

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

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	5.16
Rank	#69	Overall
	#37	Relational DBMS

Score	7.92
Rank	#51	Overall
	#2	Time Series DBMS

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

Website

github.com/spotify/heroic

azure.microsoft.com/services/data-explorer

prometheus.io

redis.com
redis.io

www.sap.com/products/advantage-database-server.html

Technical documentation

spotify.github.io/heroic

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

prometheus.io/docs

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

Developer

Spotify

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Sybase, SAP

Initial release

2014

2019

2015

2009

1993

Current release

cloud service with continuous releases

7.2.4, January 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0

Open Source

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

commercial

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

Server operating systems

hosted

Linux
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux
Windows

Data scheme

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

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

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

via Elasticsearch

all fields are automatically indexed

yes

with RediSearch module

yes

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

with RediSQL module

yes

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

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

RESTful HTTP/JSON API

proprietary protocol

RESP - REdis Serialization Protocol

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

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

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
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

Delphi
Perl
PHP

Server-side scripts

Stored procedures

Yes, possible languages: KQL, Python, R

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

yes

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

none

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

by Federation

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

none

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

Durability

Support for making data persistent

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

caching of (temporary) tables can be configured

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

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.