DBMS > Amazon Redshift vs. Apache Drill vs. EXASOL vs. PostGIS

System Properties Comparison Amazon Redshift vs. Apache Drill vs. EXASOL vs. PostGIS

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

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

Spatial extension of PostgreSQL

Primary database model

Relational DBMS

Document store
Relational DBMS

Relational DBMS

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

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

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Website

aws.amazon.com/redshift

drill.apache.org

www.exasol.com

postgis.net

Technical documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

www.exasol.com/resources

postgis.net/documentation

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Exasol

Initial release

2012

2000

2005

Current release

1.20.3, January 2023

3.4.2, February 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

Open Source

GPL v2.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

Server operating systems

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

C++

Java
Lua
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

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

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

yes

based on PostgreSQL

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.