DBMS > GeoMesa vs. HugeGraph vs. Microsoft Azure Data Explorer

System Properties Comparison GeoMesa vs. HugeGraph vs. Microsoft Azure Data Explorer

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

A fast-speed and highly-scalable Graph DBMS

Fully managed big data interactive analytics platform

Primary database model

Spatial DBMS

Graph DBMS

Relational DBMS

column oriented

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

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Website

www.geomesa.org

github.com/hugegraph
hugegraph.apache.org

azure.microsoft.com/services/data-explorer

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

hugegraph.apache.org/docs

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

Developer

CCRi and others

Baidu

Microsoft

Initial release

2014

2018

2019

Current release

5.0.0, May 2024

0.9

cloud service with continuous releases

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

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.

Implementation language

Scala

Java

Server operating systems

Linux
macOS
Unix

hosted

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

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

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

also supports composite index and range index

all fields are automatically indexed

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

APIs and other access methods

Java API
RESTful HTTP API
TinkerPop Gremlin

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

Supported programming languages

Groovy
Java
Python

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

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

Yes, possible languages: KQL, Python, R

Triggers

yes

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

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

yes

depending on used storage backend, e.g. Cassandra and HBase

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

depending on used storage backend, e.g. Cassandra and HBase

yes

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

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via hugegraph-spark

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

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Users, roles and permissions

Azure Active Directory 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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Critical Apache HugeGraph Flaw Let Attackers Execute Remote Code
23 April 2024, GBHackers

provided by Google News

Azure Data Explorer: Log and telemetry analytics benchmark
16 August 2022, Microsoft

Providing modern data transfer and storage service at Microsoft with Microsoft Azure - Inside Track Blog
13 July 2023, Microsoft

Controlling costs in Azure Data Explorer using down-sampling and aggregation
11 February 2019, Microsoft

Microsoft Introduces Azure Integration Environments and Business Process Tracking in Public Preview
23 November 2023, InfoQ.com

Individually great, collectively unmatched: Announcing updates to 3 great Azure Data Services
7 February 2019, Microsoft

provided by Google News

Share this page