DBMS > Amazon Redshift vs. Microsoft Azure SQL Database vs. Vitess vs. YDB

System Properties Comparison Amazon Redshift vs. Microsoft Azure SQL Database vs. Vitess vs. YDB

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, cloud-native DBMS, extending MySQL

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Relational DBMS

Document store
Relational DBMS

Secondary database models

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

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Score	0.39
Rank	#269	Overall
	#43	Document stores
	#126	Relational DBMS

Website

aws.amazon.com/redshift

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

vitess.io

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

docs.aws.amazon.com/redshift

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

vitess.io/docs

ydb.tech/en/docs

Developer

Amazon (based on PostgreSQL)

Microsoft

The Linux Foundation, PlanetScale

Yandex

Initial release

2012

2010

2013

2019

Current release

V12

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0, commercial licenses available

Open Source

Apache 2.0; commercial license available

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

Docker
Linux
macOS

Linux

Data scheme

yes

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

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

SQL-like query language (YQL)

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

RESTful HTTP API (DynamoDB compatible)

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)
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Transact SQL

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, with always 3 replicas available

Multi-source replication
Source-replica replication

Active-passive shard 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

Immediate Consistency

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

Access rights defined for Yandex Cloud users

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.