DBMS > Amazon Redshift vs. Microsoft Azure SQL Database vs. Tkrzw vs. VoltDB vs. YottaDB

System Properties Comparison Amazon Redshift vs. Microsoft Azure SQL Database vs. Tkrzw vs. VoltDB vs. YottaDB

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

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

A fast and solid embedded Key-value store

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

using the Octo plugin

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	0.07
Rank	#372	Overall
	#57	Key-value stores

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

aws.amazon.com/redshift

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

dbmx.net/tkrzw

www.voltdb.com

yottadb.com

Technical documentation

docs.aws.amazon.com/redshift

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

docs.voltdb.com

yottadb.com/resources/documentation

Developer

Amazon (based on PostgreSQL)

Microsoft

Mikio Hirabayashi

VoltDB Inc.

YottaDB, LLC

Initial release

2012

2010

2020

2010

2001

Current release

V12

0.9.3, August 2020

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Open Source

AGPL 3.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, C++

Server operating systems

hosted

Linux
macOS

Linux
OS X

for development

Docker
Linux

Data scheme

yes

schema-free

yes

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

only a subset of SQL 99

by using the Octo plugin

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC

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

C++
Java
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

user defined functions

in Python

Transact SQL

Java

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

yes, with always 3 replicas available

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using specific database classes

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

Users and groups based on OS-security mechanisms

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.