DBMS > Amazon Redshift vs. Microsoft Azure SQL Database vs. PlanetScale vs. Trino

System Properties Comparison Amazon Redshift vs. Microsoft Azure SQL Database vs. PlanetScale vs. Trino

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

Database as a Service offering with high compatibility to Microsoft SQL Server

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

Fast distributed SQL query engine for big data analytics. Forked from Presto and originally named PrestoSQL

Primary database model

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

Document store
Key-value store
Spatial DBMS
Search engine
Time Series DBMS
Wide column store

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	72.95
Rank	#16	Overall
	#11	Relational DBMS

Score	1.09
Rank	#178	Overall
	#82	Relational DBMS

Score	5.28
Rank	#61	Overall
	#35	Relational DBMS

Website

aws.amazon.com/redshift

azure.microsoft.com/en-us/products/azure-sql/database

planetscale.com

trino.io

Technical documentation

docs.aws.amazon.com/redshift

docs.microsoft.com/en-us/azure/azure-sql

planetscale.com/docs

trino.io/broadcast
trino.io/docs/current

Developer

Amazon (based on PostgreSQL)

Microsoft

PlanetScale

Trino Software Foundation

Initial release

2012

2010

2020

2012

2020 rebranded from PrestoSQL

Current release

V12

License

Commercial or Open Source

commercial

Open Source

Apache Version 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

C++

Java

Server operating systems

hosted

Docker
Linux
macOS

Linux
macOS

for devlopment

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

depending on connected data-source

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

JDBC
RESTful HTTP API
Trino CLI

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Go
Java
JavaScript (Node.js)
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

Transact SQL

yes

proprietary syntax

yes, depending on connected data-source

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on connected data-source

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, with always 3 replicas available

Multi-source replication
Source-replica replication

depending on connected data-source

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

depending on connected data-source

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

depending on connected data-source

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

depending on connected data-source

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

SQL standard access control

More information provided by the system vendor

News

23 is a go, keeping pace with Java
17 September 2024

65: Performance boosts
12 September 2024

64: Control with Open Policy Agent OPA
22 August 2024

63: Querying with JS
1 August 2024

62: A lakehouse that simply works at Prezi
11 July 2024

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.