DBMS > Amazon Redshift vs. Kinetica vs. Microsoft Azure Cosmos DB vs. Snowflake vs. YDB

System Properties Comparison Amazon Redshift vs. Kinetica vs. Microsoft Azure Cosmos DB vs. Snowflake vs. YDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Fully vectorized database across both GPUs and CPUs

Globally distributed, horizontally scalable, multi-model database service

Cloud-based data warehousing service for structured and semi-structured data

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
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Document store
Relational DBMS

Secondary database models

Spatial DBMS
Time Series 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	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Website

aws.amazon.com/redshift

www.kinetica.com

azure.microsoft.com/services/cosmos-db

www.snowflake.com

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

Technical documentation

docs.aws.amazon.com/redshift

docs.kinetica.com

learn.microsoft.com/azure/cosmos-db

docs.snowflake.net/manuals/index.html

ydb.tech/en/docs

Developer

Amazon (based on PostgreSQL)

Kinetica

Microsoft

Snowflake Computing Inc.

Yandex

Initial release

2012

2014

2019

Current release

7.1, August 2021

License

Commercial or Open Source

commercial

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

Server operating systems

hosted

Linux

hosted

Linux

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

SQL-like query language

yes

SQL-like query language (YQL)

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

CLI Client
JDBC
ODBC

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

All languages supporting JDBC/ODBC

C++
Java
JavaScript (Node.js)
Python

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

JavaScript (Node.js)
Python

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

JavaScript

user defined functions

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

JavaScript

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

Implicit feature of the cloud service

yes

Active-passive shard replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

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

Multi-item ACID transactions with snapshot isolation within a partition

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

GPU vRAM or System RAM

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

Access rights can be defined down to the item level

Users with fine-grained authorization concept, user roles and pluggable authentication

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.