DBMS > Apache Drill vs. Heroic vs. Infobright vs. Microsoft Azure Synapse Analytics vs. Snowflake

System Properties Comparison Apache Drill vs. Heroic vs. Infobright vs. Microsoft Azure Synapse Analytics vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

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

Primary database model

Document store
Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	1.00
Rank	#193	Overall
	#90	Relational DBMS

Score	22.71
Rank	#30	Overall
	#18	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

drill.apache.org

github.com/spotify/heroic

ignitetech.com/softwarelibrary/infobrightdb

azure.microsoft.com/services/synapse-analytics

www.snowflake.com

Technical documentation

drill.apache.org/docs

spotify.github.io/heroic

docs.microsoft.com/azure/synapse-analytics

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Spotify

Ignite Technologies Inc.; formerly InfoBright Inc.

Microsoft

Snowflake Computing Inc.

Initial release

2012

2014

2005

2016

2014

Current release

1.20.3, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

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

Java

C++

Server operating systems

Linux
OS X
Windows

Linux
Windows

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

via Elasticsearch

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

C++

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C#
Java
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Transact SQL

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding, horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

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

exploiting MySQL or PostgreSQL frontend capabilities

yes

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.