DBMS > GridGain vs. PostgreSQL vs. Teradata

System Properties Comparison GridGain vs. PostgreSQL vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used open source RDBMS

Developed as objectoriented DBMS (Postgres), gradually enhanced with 'standards' like SQL

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

with object oriented extensions, e.g.: user defined types/functions and inheritance. Handling of key/value pairs with hstore module.

Relational DBMS

Secondary database models

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.32
Rank	#156	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#70	Relational DBMS

Score	663.42
Rank	#4	Overall
	#4	Relational DBMS

Score	34.04
Rank	#23	Overall
	#16	Relational DBMS

Website

www.gridgain.com

www.postgresql.org

www.teradata.com

Technical documentation

www.gridgain.com/docs/index.html

www.postgresql.org/docs

docs.teradata.com

Developer

GridGain Systems, Inc.

PostgreSQL Global Development Group

www.postgresql.org/developer

Teradata

Initial release

2007

1989

1989: Postgres, 1996: PostgreSQL

1984

Current release

GridGain 8.5.1

16.4, August 2024

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial, open source

Open Source

BSD

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

PostgreSQL Flex @ STACKIT offers managed PostgreSQL Instances with adjustable CPU, RAM, storage amount and speed and several extensions available, in enterprise grade to perfectly match all application requirements. All 100% GDPR-compliant.

Implementation language

Java, C++, .Net, Python, REST, SQL

Server operating systems

Linux
OS X
Solaris
Windows
z/OS

FreeBSD
HP-UX
Linux
NetBSD
OpenBSD
OS X
Solaris
Unix
Windows

hosted
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

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

yes

Secondary indexes

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

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

yes

standard with numerous extensions

yes

SQL 2016 + extensions

APIs and other access methods

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

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

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C++
Delphi
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

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

user defined functions

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

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

partitioning by range, list and (since PostgreSQL 11) by hash

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Source-replica replication

other methods possible by using 3rd party extensions

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

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

Role-based access control
Security Hooks for custom implementations

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.