DBMS > Amazon Redshift vs. Oracle NoSQL vs. PostGIS vs. TerminusDB

System Properties Comparison Amazon Redshift vs. Oracle NoSQL vs. PostGIS vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Spatial extension of PostgreSQL

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

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Spatial DBMS

Graph DBMS

Secondary database models

Relational DBMS

Document store
RDF store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

aws.amazon.com/redshift

www.oracle.com/database/nosql/technologies/nosql

postgis.net

terminusdb.com

Technical documentation

docs.aws.amazon.com/redshift

docs.oracle.com/en/database/other-databases/nosql-database/index.html

postgis.net/documentation

terminusdb.github.io/terminusdb/#

Developer

Amazon (based on PostgreSQL)

Oracle

DataChemist Ltd.

Initial release

2012

2011

2005

2018

Current release

23.3, December 2023

3.4.2, February 2024

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

GPL v2.0

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

hosted

Linux
Solaris SPARC/x86

Linux

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

yes

optional

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

SQL-like DML and DDL statements

yes

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
Go
Java
JavaScript (Node.js)
Python

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

based on PostgreSQL

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

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

configurable

ACID within a storage node (=shard)

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

off heap cache

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

yes

based on PostgreSQL

Role-based access control

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.