DBMS > Amazon Aurora vs. Amazon Redshift vs. PlanetScale vs. Teradata Aster

System Properties Comparison Amazon Aurora vs. Amazon Redshift vs. PlanetScale vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Large scale data warehouse service for use with business intelligence tools

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Platform for big data analytics on multistructured data sources and types

Primary database model

Relational DBMS

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	7.57
Rank	#51	Overall
	#32	Relational DBMS

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Website

aws.amazon.com/rds/aurora

aws.amazon.com/redshift

planetscale.com

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

docs.aws.amazon.com/redshift

planetscale.com/docs

Developer

Amazon

Amazon (based on PostgreSQL)

PlanetScale

Teradata

Initial release

2015

2012

2020

2005

License

Commercial or Open Source

commercial

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

Server operating systems

hosted

Docker
Linux
macOS

Linux

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

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

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#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes

user defined functions

in Python

yes

proprietary syntax

R packages

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication
Source-replica replication

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.