DBMS > Google Cloud Datastore vs. MarkLogic vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer

System Properties Comparison Google Cloud Datastore vs. MarkLogic vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Operational and transactional Enterprise NoSQL database

Globally distributed, horizontally scalable, multi-model database service

Fully managed big data interactive analytics platform

Primary database model

Document store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

column oriented

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

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

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

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

Website

cloud.google.com/datastore

www.marklogic.com

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/services/data-explorer

Technical documentation

cloud.google.com/datastore/docs

docs.marklogic.com

learn.microsoft.com/azure/cosmos-db

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

Developer

Google

MarkLogic Corp.

Microsoft

Initial release

2008

2001

2014

2019

Current release

11.0, December 2022

cloud service with continuous releases

License

Commercial or Open Source

commercial

restricted free version is available

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

C++

Server operating systems

hosted

Linux
OS X
Windows

hosted

Data scheme

schema-free

Schema can be enforced

schema-free

Fixed schema with schema-less datatypes (dynamic)

Typing

predefined data types such as float or date

yes, details here

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

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 properties auto-indexed by default

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language (GQL)

yes

SQL92

SQL-like query language

Kusto Query Language (KQL), SQL subset

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

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

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

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

.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

Server-side scripts

Stored procedures

using Google App Engine

yes

via XQuery or JavaScript

JavaScript

Yes, possible languages: KQL, Python, R

Triggers

Callbacks using the Google Apps Engine

yes

JavaScript

yes

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

Implicit feature of the cloud service

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

using Google Cloud Dataflow

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

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

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

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

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

can act as a resource manager in an XA/JTA transaction

Multi-item ACID transactions with snapshot isolation within a partition

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.

yes, with Range Indexes

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Role-based access control at the document and subdocument levels

Access rights can be defined down to the item level

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.