DBMS > HEAVY.AI vs. MarkLogic vs. Microsoft Azure Cosmos DB

System Properties Comparison HEAVY.AI vs. MarkLogic vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Operational and transactional Enterprise NoSQL database

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	1.41
Rank	#153	Overall
	#71	Relational DBMS

Score	4.15
Rank	#70	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#8	Search engines

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

Website

github.com/heavyai/heavydb
www.heavy.ai

www.progress.com/marklogic

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.heavy.ai

www.progress.com/marklogic/documentation

learn.microsoft.com/azure/cosmos-db

Developer

HEAVY.AI, Inc.

MarkLogic Corp.

Microsoft

Initial release

2016

2001

2014

Current release

5.10, January 2022

11.0, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

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++ and CUDA

C++

Server operating systems

Linux

Linux
OS X
Windows

hosted

Data scheme

yes

schema-free

Schema can be enforced

schema-free

Typing

predefined data types such as float or date

yes

JSON 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

SQL

Support of SQL

yes

SQL92

SQL-like query language

APIs and other access methods

JDBC
ODBC
Thrift
Vega

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

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

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

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

Transaction concepts

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

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

yes, with Range Indexes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control at the document and subdocument levels

Access rights can be defined down to the item level

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.