DBMS > HEAVY.AI vs. Heroic vs. mSQL vs. Riak KV vs. Snowflake

System Properties Comparison HEAVY.AI vs. Heroic vs. mSQL vs. Riak KV vs. Snowflake

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

Distributed, fault tolerant key-value store

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

Primary database model

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

github.com/spotify/heroic

hughestech.com.au/products/msql

www.snowflake.com

Technical documentation

docs.heavy.ai

spotify.github.io/heroic

www.tiot.jp/riak-docs/riak/kv/latest

docs.snowflake.net/manuals/index.html

Developer

HEAVY.AI, Inc.

Spotify

Hughes Technologies

OpenSource, formerly Basho Technologies

Snowflake Computing Inc.

Initial release

2016

2014

1994

2009

2014

Current release

5.10, January 2022

4.4, October 2021

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

commercial

free licenses can be provided

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

Linux

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
OS X

hosted

Data scheme

yes

schema-free

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

Secondary indexes

yes

via Elasticsearch

yes

restricted

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

APIs and other access methods

JDBC
ODBC
Thrift
Vega

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

JDBC
ODBC

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

C
C++
Delphi
Java
Perl
PHP
Tcl

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Erlang

user defined functions

Triggers

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

none

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

none

selectable replication factor

yes

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

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

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 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 Riak Security

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.