DBMS > Amazon Redshift vs. GridGain vs. PostGIS vs. Teradata Aster vs. TinkerGraph

System Properties Comparison Amazon Redshift vs. GridGain vs. PostGIS vs. Teradata Aster vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

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

Spatial extension of PostgreSQL

Platform for big data analytics on multistructured data sources and types

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Spatial DBMS

Relational DBMS

Graph DBMS

Secondary database models

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

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

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

aws.amazon.com/redshift

www.gridgain.com

postgis.net

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

docs.aws.amazon.com/redshift

www.gridgain.com/docs/index.html

postgis.net/documentation

Developer

Amazon (based on PostgreSQL)

GridGain Systems, Inc.

Teradata

Initial release

2012

2007

2005

2009

Current release

GridGain 8.5.1

3.4.2, February 2024

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

commercial

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++, .Net

Java

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

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

yes

APIs and other access methods

JDBC
ODBC

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

ADO.NET
JDBC
ODBC
OLE DB

TinkerPop 3

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Java
Python
R

Groovy
Java

Server-side scripts

Stored procedures

user defined functions

in Python

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

user defined functions

R packages

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

yes

based on PostgreSQL

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

none

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in graphs

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

optional

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

yes

based on PostgreSQL

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.