DBMS > Amazon Redshift vs. Apache Impala vs. Geode vs. Percona Server for MySQL

System Properties Comparison Amazon Redshift vs. Apache Impala vs. Geode vs. Percona Server for MySQL

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

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	2.10
Rank	#119	Overall
	#57	Relational DBMS

Website

aws.amazon.com/redshift

impala.apache.org

geode.apache.org

www.percona.com/software/mysql-database/percona-server

Technical documentation

docs.aws.amazon.com/redshift

impala.apache.org/impala-docs.html

geode.apache.org/docs

www.percona.com/downloads/Percona-Server-LATEST

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Percona

Initial release

2012

2013

2002

2008

Current release

4.1.0, June 2022

1.1, February 2017

8.0.36-28, 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

GPL version 2

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 and C++

Server operating systems

hosted

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Data scheme

yes

schema-free

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

SQL-like query language (OQL)

yes

APIs and other access methods

JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions and integration of map-reduce

user defined functions

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication

Multi-source replication
Source-replica replication
XtraDB Cluster

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

yes, on a single node

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

Access rights per client and object definable

Users with fine-grained authorization concept

no user groups or 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.