DBMS > Amazon Redshift vs. Apache Impala vs. Derby vs. EsgynDB

System Properties Comparison Amazon Redshift vs. Apache Impala vs. Derby vs. EsgynDB

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

Analytic DBMS for Hadoop

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Primary database model

Relational DBMS

Secondary database models

Document store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	4.71
Rank	#69	Overall
	#37	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Website

aws.amazon.com/redshift

impala.apache.org

db.apache.org/derby

www.esgyn.cn

Technical documentation

docs.aws.amazon.com/redshift

impala.apache.org/impala-docs.html

db.apache.org/derby/manuals/index.html

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Apache Software Foundation

Esgyn

Initial release

2012

2013

1997

2015

Current release

4.1.0, June 2022

10.17.1.0, November 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache version 2

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

C++

Java

C++, Java

Server operating systems

hosted

Linux

All OS with a Java VM

Linux

Data scheme

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-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

JDBC

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

Java

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions and integration of map-reduce

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Source-replica replication

Multi-source replication between multi datacenters

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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.