DBMS > HEAVY.AI vs. Heroic vs. Microsoft Azure Cosmos DB vs. mSQL vs. Prometheus

System Properties Comparison HEAVY.AI vs. Heroic vs. Microsoft Azure Cosmos DB vs. mSQL vs. Prometheus

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

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

Globally distributed, horizontally scalable, multi-model database service

mSQL (Mini SQL) is a simple and lightweight RDBMS

Open-source Time Series DBMS and monitoring system

Primary database model

Relational DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

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

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Website

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

github.com/spotify/heroic

azure.microsoft.com/services/cosmos-db

hughestech.com.au/products/msql

prometheus.io

Technical documentation

docs.heavy.ai

spotify.github.io/heroic

learn.microsoft.com/azure/cosmos-db

prometheus.io/docs

Developer

HEAVY.AI, Inc.

Spotify

Microsoft

Hughes Technologies

Initial release

2016

2014

1994

2015

Current release

5.10, January 2022

4.4, October 2021

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

commercial

free licenses can be provided

Open Source

Apache 2.0

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

Java

Server operating systems

Linux

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

Numeric data only

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.

Import of XML data possible

Secondary indexes

yes

via Elasticsearch

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

JDBC
ODBC
Thrift
Vega

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

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

JDBC
ODBC

RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

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

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

Implicit feature of the cloud service

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

none

yes

by Federation

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

none

Foreign keys

Referential integrity

Transaction concepts

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

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

User concepts

Access control

fine grained access rights according to SQL-standard

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.