DBMS > Amazon Redshift vs. Apache Drill vs. Apache Phoenix vs. Stardog

System Properties Comparison Amazon Redshift vs. Apache Drill vs. Apache Phoenix vs. Stardog

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

A scale-out RDBMS with evolutionary schema built on Apache HBase

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

Relational DBMS

Document store
Relational DBMS

Relational DBMS

Graph DBMS
RDF store

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	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	2.07
Rank	#122	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

aws.amazon.com/redshift

drill.apache.org

phoenix.apache.org

www.stardog.com

Technical documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

phoenix.apache.org

docs.stardog.com

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Stardog-Union

Initial release

2012

2014

2010

Current release

1.20.3, January 2023

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

7.3.0, May 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache Version 2.0

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Server operating systems

hosted

Linux
OS X
Windows

Linux
Unix
Windows

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

late-bound, schema-on-read capabilities

schema-free and OWL/RDFS-schema support

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.

Import/export of XML data possible

Secondary indexes

restricted

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL SELECT statement is SQL:2003 compliant

yes

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

JDBC

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

All languages supporting JDBC/ODBC

C++

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication in HA-Cluster

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 or Eventual Consistency

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

relationships in graphs

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 Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Access rights for users and roles

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.