DBMS > Microsoft Azure Data Explorer vs. PouchDB vs. Redis vs. Transbase vs. YDB

System Properties Comparison Microsoft Azure Data Explorer vs. PouchDB vs. Redis vs. Transbase vs. YDB

Editorial information provided by DB-Engines

Name

Description

Fully managed big data interactive analytics platform

JavaScript DBMS with an API inspired by CouchDB

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 resource-optimized, high-performance, universally applicable RDBMS

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Relational DBMS

column oriented

Document store

Key-value store

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Relational DBMS

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

Score	2.28
Rank	#115	Overall
	#21	Document stores

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

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Website

azure.microsoft.com/services/data-explorer

pouchdb.com

redis.com
redis.io

www.transaction.de/en/products/transbase.html

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

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

pouchdb.com/guides

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

www.transaction.de/en/products/transbase/features.html

ydb.tech/en/docs

Developer

Microsoft

Apache Software Foundation

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Transaction Software GmbH

Yandex

Initial release

2019

2012

2009

1987

2019

Current release

cloud service with continuous releases

7.1.1, June 2019

7.2.4, January 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

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

commercial

free development license

Open Source

Apache 2.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

JavaScript

C and C++

Server operating systems

hosted

server-less, requires a JavaScript environment (browser, Node.js)

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

FreeBSD
Linux
macOS
Solaris
Windows

Linux

Data scheme

Fixed schema with schema-less datatypes (dynamic)

schema-free

yes

Flexible Schema (defined schema, partial schema, 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

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

via views

yes

with RediSearch module

yes

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

with RediSQL module

yes

SQL-like query language (YQL)

APIs and other access methods

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

HTTP REST

only for PouchDB Server
JavaScript API

proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

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

JavaScript

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
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

Yes, possible languages: KQL, Python, R

View functions in JavaScript

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

yes

Triggers

yes

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

yes

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

with a proxy-based framework, named couchdb-lounge

Sharding

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

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.

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Source-replica replication

Active-passive shard replication

MapReduce

Offers an API for user-defined Map/Reduce methods

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

yes

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual 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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

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

Access rights defined for Yandex Cloud users

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.