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

System Properties Comparison Amazon Redshift vs. Teradata vs. TerminusDB vs. VoltDB

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 hybrid cloud data analytics software platform (Teradata Vantage)

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

Secondary database models

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	41.47
Rank	#22	Overall
	#15	Relational DBMS

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Score	1.38
Rank	#156	Overall
	#72	Relational DBMS

Website

aws.amazon.com/redshift

www.teradata.com

terminusdb.com

www.voltdb.com

Technical documentation

docs.aws.amazon.com/redshift

docs.teradata.com

terminusdb.github.io/terminusdb/#

docs.voltdb.com

Developer

Amazon (based on PostgreSQL)

Teradata

DataChemist Ltd.

VoltDB Inc.

Initial release

2012

1984

2018

2010

Current release

Teradata Vantage 1.0 MU2, January 2019

11.0.0, January 2023

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

GPL V3

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

hosted

hosted
Linux

Linux

Linux
OS X

for development

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

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL 2016 + extensions

SQL-like query language (WOQL)

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

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

JavaScript
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

UDFs, stored procedures, table functions in parallel

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Hashing

Graph Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Journaling Streams

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

in-memory journaling

yes

Snapshots and command logging

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

Role-based access control

Users and roles with access to stored procedures

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.