DBMS > Dgraph vs. EsgynDB vs. Microsoft Access vs. Microsoft Azure Data Explorer vs. OpenSearch

System Properties Comparison Dgraph vs. EsgynDB vs. Microsoft Access vs. Microsoft Azure Data Explorer vs. OpenSearch

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Fully managed big data interactive analytics platform

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

Primary database model

Graph DBMS

Relational DBMS

column oriented

Search engine

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

Vector DBMS

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

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	16.03
Rank	#37	Overall
	#4	Search engines

Website

dgraph.io

www.esgyn.cn

www.microsoft.com/en-us/microsoft-365/access

azure.microsoft.com/services/data-explorer

github.com/opensearch-project
opensearch.org

Technical documentation

dgraph.io/docs

developer.microsoft.com/en-us/access

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

opensearch.org/docs/latest

Developer

Dgraph Labs, Inc.

Esgyn

Microsoft

Amazon Web Services

Initial release

2016

2015

1992

2019

2021

Current release

1902 (16.0.11328.20222), March 2019

cloud service with continuous releases

2.5.0, January 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

commercial

Open Source

Apache Version 2.0

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.

STACKIT OpenSearch offers OpenSearch in a managed version in enterprise grade, 100% GDPR-compliant, for a wide range of applications like analytics, website search, offering scalability and fast data access.
Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

C++, Java

C++

Java

Server operating systems

Linux
OS X
Windows

Linux

Windows

Not a real database server, but making use of DLLs

hosted

All OS with a Java VM

Data scheme

schema-free

yes

Fixed schema with schema-less datatypes (dynamic)

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

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

yes

all fields are automatically indexed

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

but not compliant to any SQL standard

Kusto Query Language (KQL), SQL subset

SQL-like query language

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

ADO.NET
JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

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

Java API
RESTful HTTP/JSON API

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

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

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

Server-side scripts

Stored procedures

Java Stored Procedures

yes

since Access 2010 using the ACE-engine

Yes, possible languages: KQL, Python, R

yes

Triggers

yes

since Access 2010 using the ACE-engine

yes

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

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication between multi datacenters

none

yes

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

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

Planned for future releases

fine grained access rights according to SQL-standard

a simple user-level security was built in till version Access 2003

Azure Active Directory Authentication

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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.