DBMS > HEAVY.AI vs. Heroic vs. Postgres-XL vs. Snowflake

System Properties Comparison HEAVY.AI vs. Heroic vs. Postgres-XL vs. Snowflake

Please select another system to include it in the comparison.

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	1.41
Rank	#153	Overall
	#71	Relational DBMS

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	0.43
Rank	#260	Overall
	#119	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

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

github.com/spotify/heroic

www.postgres-xl.org

www.snowflake.com

Technical documentation

docs.heavy.ai

spotify.github.io/heroic

www.postgres-xl.org/documentation

docs.snowflake.net/manuals/index.html

Developer

HEAVY.AI, Inc.

Spotify

Snowflake Computing Inc.

Initial release

2016

2014

since 2012, originally named StormDB

2014

Current release

5.10, January 2022

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

Open Source

Mozilla public license

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

Linux
macOS

hosted

Data scheme

yes

schema-free

yes

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

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

XML type, but no XML query functionality

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

distributed, parallel query execution

yes

APIs and other access methods

JDBC
ODBC
Thrift
Vega

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

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

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.