DBMS > Amazon Redshift vs. EDB Postgres vs. EsgynDB vs. Greenplum vs. GridGain

System Properties Comparison Amazon Redshift vs. EDB Postgres vs. EsgynDB vs. Greenplum vs. GridGain

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

The EDB Postgres Platform is an enterprise-class data management platform based on the open source database PostgreSQL with flexible deployment options and Oracle compatibility features, complemented by tool kits for management, integration, and migration.

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

GridGain is an in-memory computing platform, built on Apache Ignite

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.90
Rank	#135	Overall
	#63	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

www.enterprisedb.com/docs

docs.greenplum.org

www.gridgain.com/docs/index.html

Developer

Amazon (based on PostgreSQL)

EnterpriseDB

Esgyn

Pivotal Software Inc.

GridGain Systems, Inc.

Initial release

2012

2005

2015

2005

2007

Current release

14, December 2021

7.0.0, September 2023

GridGain 8.5.1

License

Commercial or Open Source

commercial

BSD for PostgreSQL-components

commercial

Open Source

Apache 2.0

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

Java, C++, .Net

Server operating systems

hosted

Linux
Windows

Linux

Linux
OS X
Solaris
Windows

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

specific XML-type available, but no XML query functionality.

yes

since Version 4.2

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

standard with numerous extensions

yes

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET
JDBC
ODBC

JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Delphi
Java
Perl
PHP
Python
Tcl

All languages supporting JDBC/ODBC/ADO.Net

C
Java
Perl
Python
R

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Java Stored Procedures

yes

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

by hash, list or range

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Multi-source replication between multi datacenters

Source-replica replication

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes, multi-version concurrency control (MVCC)

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

Security Hooks for custom implementations

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.