DBMS > Apache Drill vs. Oracle Rdb vs. RethinkDB vs. Snowflake

System Properties Comparison Apache Drill vs. Oracle Rdb vs. RethinkDB 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

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store

Relational DBMS

Secondary database models

Spatial 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	1.08
Rank	#187	Overall
	#85	Relational DBMS

Score	2.84
Rank	#106	Overall
	#19	Document stores

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

drill.apache.org

www.oracle.com/database/technologies/related/rdb.html

rethinkdb.com

www.snowflake.com

Technical documentation

drill.apache.org/docs

www.oracle.com/database/technologies/related/rdb-doc.html

rethinkdb.com/docs

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Oracle, originally developed by Digital Equipment Corporation (DEC)

The Linux Foundation

since July 2017

Snowflake Computing Inc.

Initial release

2012

1984

2009

2014

Current release

1.20.3, January 2023

7.4.1.1, 2021

2.4.1, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache Version 2

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

HP Open VMS

Linux
OS X
Windows

hosted

Data scheme

schema-free

Flexible Schema (defined schema, partial schema, schema free)

schema-free

yes

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

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

C++

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

Client-side triggers through changefeeds

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

range based

yes

Replication methods

Methods for redundantly storing data on multiple nodes

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

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

User concepts

Access control

Depending on the underlying data source

yes

users and table-level permissions

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.