DBMS > Graph Engine vs. HEAVY.AI vs. Microsoft Azure Cosmos DB vs. Warp 10

System Properties Comparison Graph Engine vs. HEAVY.AI vs. Microsoft Azure Cosmos DB vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Globally distributed, horizontally scalable, multi-model database service

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

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

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

www.graphengine.io

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

azure.microsoft.com/services/cosmos-db

www.warp10.io

Technical documentation

www.graphengine.io/docs/manual

docs.heavy.ai

learn.microsoft.com/azure/cosmos-db

www.warp10.io/content/02_Getting_started

Developer

Microsoft

HEAVY.AI, Inc.

Microsoft

SenX

Initial release

2010

2016

2014

2015

Current release

5.10, January 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

Apache License 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

.NET and C

C++ and CUDA

Java

Server operating systems

.NET

Linux

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON 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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
Thrift
Vega

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

HTTP API
Jupyter
WebSocket

Supported programming languages

C#
C++
F#
Visual Basic

All languages supporting JDBC/ODBC/Thrift
Python

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

Server-side scripts

Stored procedures

yes

JavaScript

yes

WarpScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Round robin

Sharding

Implicit feature of the cloud service

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

selectable replication factor

based on HBase

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

based on HBase

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.