DBMS > Amazon Redshift vs. PostGIS vs. TerminusDB vs. Trafodion

System Properties Comparison Amazon Redshift vs. PostGIS vs. TerminusDB vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Spatial extension of PostgreSQL

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Transactional SQL-on-Hadoop DBMS

Primary database model

Secondary database models

Relational DBMS

Document store
RDF store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

aws.amazon.com/redshift

postgis.net

terminusdb.com

trafodion.apache.org

Technical documentation

docs.aws.amazon.com/redshift

postgis.net/documentation

terminusdb.github.io/terminusdb/#

trafodion.apache.org/documentation.html

Developer

Amazon (based on PostgreSQL)

DataChemist Ltd.

Apache Software Foundation, originally developed by HP

Initial release

2012

2005

2018

2014

Current release

3.4.2, February 2024

11.0.0, January 2023

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

Open Source

GPL V3

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

Prolog, Rust

C++, Java

Server operating systems

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

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language (WOQL)

yes

APIs and other access methods

JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

JavaScript
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

Journaling Streams

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

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

Durability

Support for making data persistent

yes

in-memory journaling

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

yes

based on PostgreSQL

Role-based 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.