DBMS > Amazon Redshift vs. HEAVY.AI vs. Heroic vs. MarkLogic vs. Snowflake

System Properties Comparison Amazon Redshift vs. HEAVY.AI vs. Heroic vs. MarkLogic vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

Operational and transactional Enterprise NoSQL database

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

Primary database model

Relational DBMS

Time Series DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

aws.amazon.com/redshift

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

github.com/spotify/heroic

www.marklogic.com

www.snowflake.com

Technical documentation

docs.aws.amazon.com/redshift

docs.heavy.ai

spotify.github.io/heroic

docs.marklogic.com

docs.snowflake.net/manuals/index.html

Developer

Amazon (based on PostgreSQL)

HEAVY.AI, Inc.

Spotify

MarkLogic Corp.

Snowflake Computing Inc.

Initial release

2012

2016

2014

2001

2014

Current release

5.10, January 2022

11.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

commercial

restricted free version is 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

C++

Server operating systems

hosted

Linux

Linux
OS X
Windows

hosted

Data scheme

yes

schema-free

Schema can be enforced

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

Secondary indexes

restricted

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL92

yes

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Thrift
Vega

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

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/Thrift
Python

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

via XQuery or 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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

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

yes, with Range Indexes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control at the document and subdocument levels

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.