DBMS > Amazon Aurora vs. Amazon Redshift vs. Apache Impala vs. Drizzle vs. Ehcache

System Properties Comparison Amazon Aurora vs. Amazon Redshift vs. Apache Impala vs. Drizzle vs. Ehcache

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for Hadoop

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A widely adopted Java cache with tiered storage options

Primary database model

Relational DBMS

Key-value store

Secondary database models

Document store

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

Score	8.50
Rank	#49	Overall
	#31	Relational DBMS

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	14.03
Rank	#40	Overall
	#24	Relational DBMS

Score	5.23
Rank	#68	Overall
	#8	Key-value stores

Website

aws.amazon.com/rds/aurora

aws.amazon.com/redshift

impala.apache.org

www.ehcache.org

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

docs.aws.amazon.com/redshift

impala.apache.org/impala-docs.html

www.ehcache.org/documentation

Developer

Amazon

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Drizzle project, originally started by Brian Aker

Terracotta Inc, owned by Software AG

Initial release

2015

2012

2013

2008

2009

Current release

4.1.0, June 2022

7.2.4, September 2012

3.10.0, March 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available

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

FreeBSD
Linux
OS X

All OS with a Java VM

Data scheme

yes

schema-free

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

yes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

JDBC

JCache

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

All languages supporting JDBC/ODBC

C
C++
Java
PHP

Java

Server-side scripts

Stored procedures

yes

user defined functions

in Python

yes

user defined functions and integration of map-reduce

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

by using Terracotta Server

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

selectable replication factor

Multi-source replication
Source-replica replication

yes

by using Terracotta Server

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

Tunable Consistency (Strong, Eventual, Weak)

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

yes

supports JTA and can work as an XA resource

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.