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

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

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

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

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

Primary database model

Relational DBMS

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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	72.95
Rank	#16	Overall
	#11	Relational DBMS

Score	1.09
Rank	#178	Overall
	#82	Relational DBMS

Website

aws.amazon.com/redshift

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

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

planetscale.com

Technical documentation

docs.aws.amazon.com/redshift

docs.dolthub.com

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

planetscale.com/docs

Developer

Amazon (based on PostgreSQL)

DoltHub Inc

Microsoft

PlanetScale

Initial release

2012

2018

2010

2020

Current release

V12

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

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

C++

Server operating systems

hosted

Linux
macOS
Windows

hosted

Docker
Linux
macOS

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

CLI Client
HTTP REST

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

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

.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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

currently in alpha release

Transact SQL

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

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.

yes, with always 3 replicas available

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

Eventual Consistency across shards
Immediate Consistency within a shard

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

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.