DBMS > Apache Drill vs. EXASOL vs. Riak TS vs. Snowflake

System Properties Comparison Apache Drill vs. EXASOL vs. Riak TS 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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Time Series DBMS

Relational 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.99
Rank	#124	Overall
	#58	Relational DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

drill.apache.org

www.exasol.com

www.snowflake.com

Technical documentation

drill.apache.org/docs

www.exasol.com/resources

www.tiot.jp/riak-docs/riak/ts/latest

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Exasol

Open Source, formerly Basho Technologies

Snowflake Computing Inc.

Initial release

2012

2000

2015

2014

Current release

1.20.3, January 2023

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

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

Erlang

Server operating systems

Linux
OS X
Windows

Linux
OS X

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

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

restricted

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

yes, limited

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

Supported programming languages

C++

Java
Lua
Python
R

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Erlang

user defined functions

Triggers

yes

pre-commit hooks and post-commit hooks

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

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

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

Access rights for users, groups and roles according to SQL-standard

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.