DBMS > Microsoft Azure Data Explorer vs. OrigoDB vs. XTDB

System Properties Comparison Microsoft Azure Data Explorer vs. OrigoDB vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fully managed big data interactive analytics platform

A fully ACID in-memory object graph database

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

column oriented

Document store
Object oriented DBMS

Document store

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

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

azure.microsoft.com/services/data-explorer

origodb.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

origodb.com/docs

www.xtdb.com/docs

Developer

Microsoft

Robert Friberg et al

Juxt Ltd.

Initial release

2019

2009

under the name LiveDB

2019

Current release

cloud service with continuous releases

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

MIT License

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

Clojure

Server operating systems

hosted

Linux
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

Fixed schema with schema-less datatypes (dynamic)

yes

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

User defined using .NET types and collections

yes, extensible-data-notation format

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

can be achieved using .NET

Secondary indexes

all fields are automatically indexed

yes

SQL

Support of SQL

Kusto Query Language (KQL), SQL subset

limited SQL, making use of Apache Calcite

APIs and other access methods

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

.NET Client API
HTTP API
LINQ

HTTP REST
JDBC

Supported programming languages

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

.Net

Clojure
Java

Server-side scripts

Stored procedures

Yes, possible languages: KQL, Python, R

yes

Triggers

yes

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

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning

client side managed; servers are not synchronized

none

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.

Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

Write ahead log

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Role based authorization

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

Recent citations in the news

General availability: Azure Data Explorer adds new geospatial capabilities | Azure updates
23 January 2024, azure.microsoft.com

Public Preview: Azure Data Explorer connector for Apache Flink | Azure updates
8 January 2024, azure.microsoft.com

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

Azure Data Explorer: Log and telemetry analytics benchmark
16 August 2022, azure.microsoft.com

Introducing Microsoft Fabric: The data platform for the era of AI | Microsoft Azure Blog
23 May 2023, azure.microsoft.com

provided by Google News

Share this page