DBMS > HEAVY.AI vs. Microsoft Azure AI Search vs. Snowflake vs. TinkerGraph vs. VoltDB

System Properties Comparison HEAVY.AI vs. Microsoft Azure AI Search vs. Snowflake vs. TinkerGraph vs. VoltDB

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

Search-as-a-service for web and mobile app development

Cloud-based data warehousing service for structured and semi-structured data

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Secondary database models

Spatial DBMS

Vector DBMS

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

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

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

azure.microsoft.com/en-us/services/search

www.snowflake.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

www.voltdb.com

Technical documentation

docs.heavy.ai

learn.microsoft.com/en-us/azure/search

docs.snowflake.net/manuals/index.html

docs.voltdb.com

Developer

HEAVY.AI, Inc.

Microsoft

Snowflake Computing Inc.

VoltDB Inc.

Initial release

2016

2015

2014

2009

2010

Current release

5.10, January 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

Apache 2.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

Linux

hosted

Linux
OS X

for development

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

yes

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC
Thrift
Vega

RESTful HTTP API

CLI Client
JDBC
ODBC

TinkerPop 3

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

C#
Java
JavaScript
Python

JavaScript (Node.js)
Python

Groovy
Java

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

Java

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

Implicit feature of the cloud service

yes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

optional

yes

Snapshots and command logging

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

yes

using Azure authentication

Users with fine-grained authorization concept, user roles and pluggable authentication

Users and roles with access to stored procedures

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.