DBMS > Amazon Redshift vs. Microsoft Azure SQL Database vs. TerarkDB vs. Tkrzw

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

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

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

Primary database model

Relational DBMS

Key-value store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

aws.amazon.com/redshift

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

github.com/bytedance/terarkdb

dbmx.net/tkrzw

Technical documentation

docs.aws.amazon.com/redshift

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

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Amazon (based on PostgreSQL)

Microsoft

ByteDance, originally Terark

Mikio Hirabayashi

Initial release

2012

2010

2016

2020

Current release

V12

0.9.3, August 2020

License

Commercial or Open Source

commercial

restricted open source version available

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

Server operating systems

hosted

Linux
macOS

Data scheme

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

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC

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

C++
Java

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

Transact SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, with always 3 replicas available

none

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

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

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

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.