DBMS > AllegroGraph vs. Microsoft Azure Data Explorer vs. Oracle NoSQL vs. Redis

System Properties Comparison AllegroGraph vs. Microsoft Azure Data Explorer vs. Oracle NoSQL vs. Redis

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performance, persistent RDF store with additional support for Graph DBMS

Fully managed big data interactive analytics platform

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

Document store

with version 6.5
Graph DBMS
RDF store
Vector DBMS

Relational DBMS

column oriented

Document store
Key-value store
Relational DBMS

Key-value store

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

Secondary database models

Spatial DBMS

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	1.06
Rank	#187	Overall
	#30	Document stores
	#17	Graph DBMS
	#7	RDF stores
	#7	Vector DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

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

Website

allegrograph.com

azure.microsoft.com/services/data-explorer

www.oracle.com/database/nosql/technologies/nosql

redis.com
redis.io

Technical documentation

franz.com/agraph/support/documentation/current/agraph-introduction.html

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

docs.oracle.com/en/database/other-databases/nosql-database/index.html

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

Developer

Franz Inc.

Microsoft

Oracle

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2004

2019

2011

2009

Current release

8.0, December 2023

cloud service with continuous releases

23.3, December 2023

7.2.4, January 2024

License

Commercial or Open Source

commercial

Limited community edition free

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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 Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

Implementation language

Java

Server operating systems

Linux
OS X
Windows

hosted

Linux
Solaris SPARC/x86

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

yes

RDF schemas

Fixed schema with schema-less datatypes (dynamic)

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

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

optional

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.

bulk load of XML files possible

yes

Secondary indexes

yes

all fields are automatically indexed

yes

with RediSearch module

SQL

Support of SQL

SPARQL is used as query language

Kusto Query Language (KQL), SQL subset

SQL-like DML and DDL statements

with RediSQL module

APIs and other access methods

RESTful HTTP API
SPARQL

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

RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

C#
Clojure
Java
Lisp
Perl
Python
Ruby
Scala

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

C
C#
Go
Java
JavaScript (Node.js)
Python

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

JavaScript or Common Lisp

Yes, possible languages: KQL, Python, R

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

Triggers

yes

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

publish/subscribe channels provide some trigger functionality; RedisGears

Partitioning methods

Methods for storing different data on different nodes

with Federation

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

Multi-source replication
Source-replica replication

yes

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

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

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

with Hadoop integration

through RedisGears

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

depending on configuration

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

ACID

configurable

ACID within a storage node (=shard)

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

off heap cache

yes

User concepts

Access control

Users with fine-grained authorization concept, user roles and pluggable authentication

Azure Active Directory Authentication

Access rights for users and roles

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

Knowledge Graph Platform Leader FedShard - Designed for Entity-Event Knowledge Graph...
» more

Competitive advantages

AllegroGraph is uniquely suited to support adhoc queries through SPARQL, Prolog and...
» more

News

Can Neuro-Symbolic AI Solve AI’s Weaknesses?
17 April 2024

100 Companies That Matter in KM – Franz Inc.
3 April 2024

Exploring AllegroGraph v8 – Unleashing the Power of Neuro-Symbolic AI (Recorded Webinar)
9 February 2024

What is Neuro-Symbolic AI?
23 January 2024

Allegro CL v11 – Now Available! – The Neuro-Symbolic AI Programming Platform
8 January 2024

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.