DBMS > Amazon Redshift vs. Apache Druid vs. Apache Impala vs. Infobright vs. Microsoft Azure SQL Database

System Properties Comparison Amazon Redshift vs. Apache Druid vs. Apache Impala vs. Infobright vs. Microsoft Azure SQL Database

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Analytic DBMS for Hadoop

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Database as a Service offering with high compatibility to Microsoft SQL Server

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Relational DBMS

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Website

aws.amazon.com/redshift

druid.apache.org

impala.apache.org

ignitetech.com/softwarelibrary/infobrightdb

azure.microsoft.com/en-us/products/azure-sql/database

Technical documentation

docs.aws.amazon.com/redshift

druid.apache.org/docs/latest/design

impala.apache.org/impala-docs.html

docs.microsoft.com/en-us/azure/azure-sql

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation and contributors

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Ignite Technologies Inc.; formerly InfoBright Inc.

Microsoft

Initial release

2012

2013

2005

2010

Current release

29.0.1, April 2024

4.1.0, June 2022

V12

License

Commercial or Open Source

commercial

Open Source

Apache license v2

Open Source

Apache Version 2

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

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

Java

C++

Server operating systems

hosted

Linux
OS X
Unix

Linux

Linux
Windows

hosted

Data scheme

yes

schema-less columns are supported

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL for querying

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

JDBC
RESTful HTTP/JSON API

JDBC
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

All languages supporting JDBC/ODBC

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions and integration of map-reduce

Transact SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HDFS, S3 or other storage engines

selectable replication factor

Source-replica replication

yes, with always 3 replicas available

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

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.