DBMS > Apache Drill vs. Hive vs. KeyDB vs. Snowflake

System Properties Comparison Apache Drill vs. Hive vs. KeyDB 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

data warehouse software for querying and managing large distributed datasets, built on Hadoop

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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

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	59.76
Rank	#18	Overall
	#12	Relational DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

drill.apache.org

hive.apache.org

github.com/Snapchat/KeyDB
keydb.dev

www.snowflake.com

Technical documentation

drill.apache.org/docs

cwiki.apache.org/confluence/display/Hive/Home

docs.keydb.dev

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

initially developed by Facebook

EQ Alpha Technology Ltd.

Snowflake Computing Inc.

Initial release

2012

2019

2014

Current release

1.20.3, January 2023

3.1.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2

Open Source

BSD-3

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

All OS with a Java VM

Linux

hosted

Data scheme

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

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

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
Thrift

Proprietary protocol

RESP - REdis Serialization Protoco

CLI Client
JDBC
ODBC

Supported programming languages

C++

C++
Java
PHP
Python

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

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

Multi-source replication
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

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

simple password-based access control and ACL

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.