DBMS > HEAVY.AI vs. IBM Cloudant vs. Microsoft Azure AI Search vs. Snowflake vs. XTDB

System Properties Comparison HEAVY.AI vs. IBM Cloudant vs. Microsoft Azure AI Search vs. Snowflake vs. XTDB

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

Database as a Service offering based on Apache CouchDB

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

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

A general purpose database with bitemporal SQL and Datalog and graph queries

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	2.68
Rank	#106	Overall
	#20	Document stores

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

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

www.ibm.com/products/cloudant

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

www.snowflake.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.heavy.ai

cloud.ibm.com/docs/Cloudant

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

docs.snowflake.net/manuals/index.html

www.xtdb.com/docs

Developer

HEAVY.AI, Inc.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Snowflake Computing Inc.

Juxt Ltd.

Initial release

2016

2010

2015

2014

2019

Current release

5.10, January 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

MIT License

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

Erlang

Clojure

Server operating systems

Linux

hosted

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

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

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC
Thrift
Vega

RESTful HTTP/JSON API

RESTful HTTP API

CLI Client
JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

C#
Java
JavaScript
Objective-C
PHP
Ruby

C#
Java
JavaScript
Python

JavaScript (Node.js)
Python

Clojure
Java

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

user defined functions

Triggers

yes

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

yes

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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 for users can be defined per database

yes

using Azure authentication

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

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.