DBMS > Apache Drill vs. Apache Impala vs. Dragonfly vs. Snowflake

System Properties Comparison Apache Drill vs. Apache Impala vs. Dragonfly 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

Analytic DBMS for Hadoop

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	0.49
Rank	#261	Overall
	#38	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

drill.apache.org

impala.apache.org

github.com/dragonflydb/dragonfly
www.dragonflydb.io

www.snowflake.com

Technical documentation

drill.apache.org/docs

impala.apache.org/impala-docs.html

www.dragonflydb.io/docs

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

DragonflyDB team and community contributors

Snowflake Computing Inc.

Initial release

2012

2013

2023

2014

Current release

1.20.3, January 2023

4.1.0, June 2022

1.0, March 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2

Open Source

BSL 1.1

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++

Server operating systems

Linux
OS X
Windows

Linux

hosted

Data scheme

schema-free

yes

scheme-free

yes

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

Typing

predefined data types such as float or date

yes

strings, hashes, lists, sets, sorted sets, bit arrays

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

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protocol

CLI Client
JDBC
ODBC

Supported programming languages

C++

All languages supporting JDBC/ODBC

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions and integration of map-reduce

Lua

user defined functions

Triggers

publish/subscribe channels provide some trigger functionality

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of command blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Password-based authentication

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.