DBMS > HEAVY.AI vs. MySQL vs. Snowflake vs. Spark SQL

System Properties Comparison HEAVY.AI vs. MySQL vs. Snowflake vs. Spark SQL

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

Widely used open source RDBMS

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Relational DBMS

Key/Value like access via memcached API

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.77
Rank	#141	Overall
	#65	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

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

www.mysql.com

www.snowflake.com

spark.apache.org/sql

Technical documentation

docs.heavy.ai

dev.mysql.com/doc

docs.snowflake.net/manuals/index.html

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

HEAVY.AI, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Snowflake Computing Inc.

Apache Software Foundation

Initial release

2016

1995

2014

Current release

5.10, January 2022

8.4.0, April 2024

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

Apache 2.0

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++ and CUDA

C and C++

Scala

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

hosted

Linux
OS X
Windows

Data scheme

yes

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

yes

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

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC
Thrift
Vega

ADO.NET
JDBC
ODBC
Proprietary native API

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript (Node.js)
Python

Java
Python
R
Scala

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

no user groups or roles

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.