DBMS > Amazon Redshift vs. Ehcache vs. Greenplum vs. HEAVY.AI vs. Newts

System Properties Comparison Amazon Redshift vs. Ehcache vs. Greenplum vs. HEAVY.AI vs. Newts

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A widely adopted Java cache with tiered storage options

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.

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Time Series DBMS based on Cassandra

Primary database model

Secondary database models

Document store
Spatial 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	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

aws.amazon.com/redshift

www.ehcache.org

greenplum.org

github.com/heavyai/heavydb
www.heavy.ai

opennms.github.io/newts

Technical documentation

docs.aws.amazon.com/redshift

www.ehcache.org/documentation

docs.greenplum.org

docs.heavy.ai

github.com/OpenNMS/newts/wiki

Developer

Amazon (based on PostgreSQL)

Terracotta Inc, owned by Software AG

Pivotal Software Inc.

HEAVY.AI, Inc.

OpenNMS Group

Initial release

2012

2009

2005

2016

2014

Current release

3.10.0, March 2022

7.0.0, September 2023

5.10, January 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache 2.0

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

Java

Server operating systems

hosted

All OS with a Java VM

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

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

since Version 4.2

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

JCache

JDBC
ODBC

JDBC
ODBC
Thrift
Vega

HTTP REST
Java API

Supported programming languages

All languages supporting JDBC/ODBC

Java

C
Java
Perl
Python
R

All languages supporting JDBC/ODBC/Thrift
Python

Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

Round robin

Sharding

based on Cassandra

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Source-replica replication

Multi-source replication

selectable replication factor

based on Cassandra

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

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.