DBMS > HEAVY.AI vs. Microsoft Azure Cosmos DB vs. Snowflake vs. Sqrrl

System Properties Comparison HEAVY.AI vs. Microsoft Azure Cosmos DB vs. Snowflake vs. Sqrrl

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been 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

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

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

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

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

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

azure.microsoft.com/services/cosmos-db

www.snowflake.com

sqrrl.com

Technical documentation

docs.heavy.ai

learn.microsoft.com/azure/cosmos-db

docs.snowflake.net/manuals/index.html

Developer

HEAVY.AI, Inc.

Microsoft

Snowflake Computing Inc.

Amazon

originally Sqrrl Data, Inc.

Initial release

2016

2014

2012

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

Java

Server operating systems

Linux

hosted

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

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
Thrift
Vega

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

CLI Client
JDBC
ODBC

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

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

JavaScript (Node.js)
Python

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

JavaScript

user defined functions

Triggers

JavaScript

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

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

yes

selectable replication factor

making use of Hadoop

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

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

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

Atomic updates per row, document, or graph entity

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

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

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.