DBMS > Amazon Redshift vs. Microsoft Azure SQL Database vs. Riak KV vs. RisingWave

System Properties Comparison Amazon Redshift vs. Microsoft Azure SQL Database vs. Riak KV vs. RisingWave

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

Distributed, fault tolerant key-value store

A distributed RDBMS for stream processing, wire-compatible with PostgreSQL

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	0.64
Rank	#238	Overall
	#110	Relational DBMS

Website

aws.amazon.com/redshift

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

www.risingwave.com/database

Technical documentation

docs.aws.amazon.com/redshift

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

www.tiot.jp/riak-docs/riak/kv/latest

docs.risingwave.com/docs/current/intro

Developer

Amazon (based on PostgreSQL)

Microsoft

OpenSource, formerly Basho Technologies

RisingWave Labs

Initial release

2012

2010

2009

2022

Current release

V12

3.2.0, December 2022

1.2, September 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

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++

Erlang

Rust

Server operating systems

hosted

Linux
OS X

Docker
Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Standard SQL-types and JSON

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

JDBC
PostgreSQL wire protocol

Supported programming languages

All languages supporting JDBC/ODBC

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Transact SQL

Erlang

UDFs in Python or Java

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, with always 3 replicas available

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

links between data sets can be stored

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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

yes, using Riak Security

Users and 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.