DBMS > Amazon Redshift vs. Apache Drill vs. Kinetica vs. Quasardb vs. Spark SQL

System Properties Comparison Amazon Redshift vs. Apache Drill vs. Kinetica vs. Quasardb vs. Spark SQL

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

Fully vectorized database across both GPUs and CPUs

Distributed, high-performance timeseries database

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Relational DBMS

Document store
Relational DBMS

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS
Time Series 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	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

docs.kinetica.com

doc.quasar.ai/master

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Kinetica

quasardb

Apache Software Foundation

Initial release

2012

2009

2014

Current release

1.20.3, January 2023

7.1, August 2021

3.14.1, January 2024

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Apache 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, C++

C++

Scala

Server operating systems

hosted

Linux
OS X
Windows

Linux

BSD
Linux
OS X
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL SELECT statement is SQL:2003 compliant

SQL-like DML and DDL statements

SQL-like query language

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

HTTP API

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C++

C++
Java
JavaScript (Node.js)
Python

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Java
Python
R
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Source-replica replication with selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency or Eventual Consistency depending on configuration

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

by using LevelDB

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

GPU vRAM or System RAM

yes

Transient mode

User concepts

Access control

fine grained access rights according to SQL-standard

Depending on the underlying data source

Access rights for users and roles on table level

Cryptographically strong user authentication and audit trail

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.