DBMS > Amazon Redshift vs. Apache Drill vs. RethinkDB vs. Warp 10

System Properties Comparison Amazon Redshift vs. Apache Drill vs. RethinkDB vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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.

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

Document store
Relational DBMS

Document store

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	2.74
Rank	#105	Overall
	#19	Document stores

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

aws.amazon.com/redshift

drill.apache.org

rethinkdb.com

www.warp10.io

Technical documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

rethinkdb.com/docs

www.warp10.io/content/02_Getting_started

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

The Linux Foundation

since July 2017

SenX

Initial release

2012

2009

2015

Current release

1.20.3, January 2023

2.4.1, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache Version 2

Open Source

Apache License 2.0

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

Java

Server operating systems

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL SELECT statement is SQL:2003 compliant

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

HTTP API
Jupyter
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

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

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

WarpScript

Triggers

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

Sharding

range based

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

yes

Durability

Support for making data persistent

yes

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.

yes

Depending on the underlying data source

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Depending on the underlying data source

yes

users and table-level permissions

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.