DBMS > Amazon Redshift vs. Dolt vs. Teradata vs. TerminusDB

System Properties Comparison Amazon Redshift vs. Dolt vs. Teradata 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 MySQL compatible DBMS with Git-like versioning of data and schema

A hybrid cloud data analytics software platform (Teradata Vantage)

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

Primary database model

Relational DBMS

Graph DBMS

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
RDF store

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	0.93
Rank	#194	Overall
	#90	Relational DBMS

Score	41.47
Rank	#22	Overall
	#15	Relational DBMS

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Website

aws.amazon.com/redshift

github.com/dolthub/dolt
www.dolthub.com

www.teradata.com

terminusdb.com

Technical documentation

docs.aws.amazon.com/redshift

docs.dolthub.com

docs.teradata.com

terminusdb.github.io/terminusdb/#

Developer

Amazon (based on PostgreSQL)

DoltHub Inc

Teradata

DataChemist Ltd.

Initial release

2012

2018

1984

2018

Current release

Teradata Vantage 1.0 MU2, January 2019

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

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

Prolog, Rust

Server operating systems

hosted

Linux
macOS
Windows

hosted
Linux

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

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL 2016 + extensions

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

CLI Client
HTTP REST

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

currently in alpha release

yes

UDFs, stored procedures, table functions in parallel

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Hashing

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication
Source-replica replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

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

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

Only one user is configurable, and must be specified in the config file at startup

fine grained access rights according to SQL-standard

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.