DBMS > Apache Drill vs. HEAVY.AI vs. JaguarDB vs. Snowflake

System Properties Comparison Apache Drill vs. HEAVY.AI vs. JaguarDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Performant, highly scalable DBMS for AI and IoT applications

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

drill.apache.org

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

www.jaguardb.com

www.snowflake.com

Technical documentation

drill.apache.org/docs

docs.heavy.ai

www.jaguardb.com/support.html

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

HEAVY.AI, Inc.

DataJaguar, Inc.

Snowflake Computing Inc.

Initial release

2012

2016

2015

2014

Current release

1.20.3, January 2023

5.10, January 2022

3.3 July 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2; enterprise edition available

Open Source

GPL V3.0

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

C++

the server part. Clients available in other languages

Server operating systems

Linux
OS X
Windows

Linux

hosted

Data scheme

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

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
Thrift
Vega

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

C++

All languages supporting JDBC/ODBC/Thrift
Python

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

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

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

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

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

rights management via user accounts

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.