DBMS > HEAVY.AI vs. Microsoft Azure AI Search vs. Snowflake vs. Teradata vs. TerminusDB

System Properties Comparison HEAVY.AI vs. Microsoft Azure AI Search vs. Snowflake vs. Teradata vs. TerminusDB

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 hybrid cloud data analytics software platform (Teradata Vantage)

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Spatial DBMS

Vector DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
RDF store

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

Score	2.10
Rank	#126	Overall
	#61	Relational DBMS

Score	5.71
Rank	#64	Overall
	#8	Search engines

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	47.84
Rank	#21	Overall
	#15	Relational DBMS

Score	0.22
Rank	#323	Overall
	#28	Graph DBMS

Website

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

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

www.snowflake.com

www.teradata.com

terminusdb.com

Technical documentation

docs.heavy.ai

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

docs.snowflake.net/manuals/index.html

docs.teradata.com

terminusdb.github.io/terminusdb/#

Developer

HEAVY.AI, Inc.

Microsoft

Snowflake Computing Inc.

Teradata

DataChemist Ltd.

Initial release

2016

2015

2014

1984

2018

Current release

5.10, January 2022

Teradata Vantage 1.0 MU2, January 2019

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

Linux

hosted

hosted
Linux

Linux

Data scheme

yes

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

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

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

SQL 2016 + extensions

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC
Thrift
Vega

RESTful HTTP API

CLI Client
JDBC
ODBC

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

C#
Java
JavaScript
Python

JavaScript (Node.js)
Python

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

yes

UDFs, stored procedures, table functions in parallel

yes

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

Implicit feature of the cloud service

yes

Sharding

Hashing

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

yes

Multi-source replication
Source-replica replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

fine grained access rights according to SQL-standard

Role-based access control

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.