DBMS > HEAVY.AI vs. Microsoft Azure Cosmos DB vs. TigerGraph vs. Yaacomo

System Properties Comparison HEAVY.AI vs. Microsoft Azure Cosmos DB vs. TigerGraph vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS

Relational 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	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

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

azure.microsoft.com/services/cosmos-db

www.tigergraph.com

yaacomo.com

Technical documentation

docs.heavy.ai

learn.microsoft.com/azure/cosmos-db

docs.tigergraph.com

Developer

HEAVY.AI, Inc.

Microsoft

Q2WEB GmbH

Initial release

2016

2014

2017

2009

Current release

5.10, January 2022

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition 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

hosted

Linux

Android
Linux
Windows

Data scheme

yes

schema-free

yes

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

yes

SQL

Support of SQL

yes

SQL-like query language

SQL-like query language (GSQL)

yes

APIs and other access methods

JDBC
ODBC
Thrift
Vega

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

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

JDBC
ODBC

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++
Java

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

Implicit feature of the cloud service

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

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

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

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

Role-based access control

fine grained access rights according to SQL-standard

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.