DBMS > EJDB vs. Faircom EDGE vs. Microsoft Azure Data Explorer vs. Microsoft Azure Table Storage vs. Redis

System Properties Comparison EJDB vs. Faircom EDGE vs. Microsoft Azure Data Explorer vs. Microsoft Azure Table Storage vs. Redis

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

Fully managed big data interactive analytics platform

A Wide Column Store for rapid development using massive semi-structured datasets

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

Key-value store
Relational DBMS

Relational DBMS

column oriented

Wide column store

Key-value store

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

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.27
Rank	#297	Overall
	#44	Document stores

Score	0.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

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

Website

github.com/Softmotions/ejdb

www.faircom.com/products/faircom-edge

azure.microsoft.com/services/data-explorer

azure.microsoft.com/en-us/services/storage/tables

redis.com
redis.io

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

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

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

Developer

Softmotions

FairCom Corporation

Microsoft

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

Initial release

2012

1979

2019

2012

2009

Current release

V3, October 2020

cloud service with continuous releases

7.2.4, January 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

Restricted, free version available

commercial

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

ANSI C, C++

Server operating systems

server-less

Android
Linux

ARM, x86
Raspbian
Windows

hosted

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Data scheme

schema-free

Flexible Schema (defined schema, partial schema, schema free)

Fixed schema with schema-less datatypes (dynamic)

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes, ANSI Standard SQL Types

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

yes

all fields are automatically indexed

yes

with RediSearch module

SQL

Support of SQL

yes

ANSI SQL queries

Kusto Query Language (KQL), SQL subset

with RediSQL module

APIs and other access methods

in-process shared library

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

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

RESTful HTTP API

proprietary protocol

RESP - REdis Serialization Protocol

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

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

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

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

none

File partitioning

Customizable business rules for partitioning

Sharding

Implicit feature of the cloud service

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

none

yes

Synchronous and asynchronous realtime replication based on transaction logs

yes

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

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

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

Immediate Consistency
Tunable Consistency

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

typically not needed, however similar functionality with collection joins possible

yes

when using SQL

Transaction concepts

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

ACID

optimistic locking

Atomic execution of command blocks and scripts and optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

across SQL and NoSQL

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

User concepts

Access control

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

Azure Active Directory Authentication

Access rights based on private key authentication or shared access signatures

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.