DBMS > Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. Stardog vs. UniData,UniVerse

System Properties Comparison Google Cloud Datastore vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. Stardog vs. UniData,UniVerse

Editorial information provided by DB-Engines

Name

Description

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

Globally distributed, horizontally scalable, multi-model database service

Fully managed big data interactive analytics platform

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

MultiValue database and application server with SQL mapping layer and meta database capabilities

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

column oriented

Graph DBMS
RDF store

Multivalue 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

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

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

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Score	3.16
Rank	#97	Overall
	#2	Multivalue DBMS

Website

cloud.google.com/datastore

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/services/data-explorer

www.stardog.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-unidata

Technical documentation

cloud.google.com/datastore/docs

learn.microsoft.com/azure/cosmos-db

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

docs.stardog.com

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

Developer

Google

Microsoft

Stardog-Union

Rocket Software

Initial release

2008

2014

2019

2010

1985

Current release

cloud service with continuous releases

7.3.0, May 2020

License

Commercial or Open Source

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Java

Server operating systems

hosted

Linux
macOS
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

Fixed schema with schema-less datatypes (dynamic)

schema-free and OWL/RDFS-schema support

schema-free

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

yes

optional

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

Import/export of XML data possible

Secondary indexes

yes

All properties auto-indexed by default

all fields are automatically indexed

yes

supports real-time indexing in full-text and geospatial

yes

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

Kusto Query Language (KQL), SQL subset

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

yes

APIs and other access methods

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

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

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

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
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

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

using Google App Engine

JavaScript

Yes, possible languages: KQL, Python, R

user defined functions and aggregates, HTTP Server extensions in Java

yes

Triggers

Callbacks using the Google Apps Engine

JavaScript

yes

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

yes

via event handlers

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

none

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.

Multi-source replication in HA-Cluster

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

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.

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

relationships in graphs

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Multi-item ACID transactions with snapshot isolation within a partition

ACID

configurable

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

User concepts

Access control

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

Access rights can be defined down to the item level

Azure Active Directory Authentication

Access rights for users and roles

Access rights according to SQL-standard and operating system based

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.