DBMS > Heroic vs. LeanXcale vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. TerminusDB

System Properties Comparison Heroic vs. LeanXcale vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Globally distributed, horizontally scalable, multi-model database service

Fully managed big data interactive analytics platform

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Time Series DBMS

Key-value store
Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

column oriented

Graph DBMS

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
RDF store

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.36
Rank	#280	Overall
	#40	Key-value stores
	#129	Relational DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

github.com/spotify/heroic

www.leanxcale.com

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/services/data-explorer

terminusdb.com

Technical documentation

spotify.github.io/heroic

learn.microsoft.com/azure/cosmos-db

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

terminusdb.github.io/terminusdb/#

Developer

Spotify

LeanXcale

Microsoft

DataChemist Ltd.

Initial release

2014

2015

2014

2019

2018

Current release

cloud service with continuous releases

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPL V3

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

Java

Prolog, Rust

Server operating systems

hosted

Linux

Data scheme

schema-free

yes

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

Typing

predefined data types such as float or date

yes

JSON types

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

via Elasticsearch

yes

All properties auto-indexed by default

all fields are automatically indexed

SQL

Support of SQL

yes

through Apache Derby

SQL-like query language

Kusto Query Language (KQL), SQL subset

SQL-like query language (WOQL)

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C
Java
Scala

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

JavaScript
Python

Server-side scripts

Stored procedures

JavaScript

Yes, possible languages: KQL, Python, R

yes

Triggers

JavaScript

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

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

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

In-memory capabilities

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

yes

User concepts

Access control

Access rights can be defined down to the item level

Azure Active Directory Authentication

Role-based access control

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.