DBMS > Amazon Redshift vs. Google Cloud Datastore vs. Kinetica vs. Microsoft Azure SQL Database vs. VictoriaMetrics

System Properties Comparison Amazon Redshift vs. Google Cloud Datastore vs. Kinetica vs. Microsoft Azure SQL Database vs. VictoriaMetrics

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Fully vectorized database across both GPUs and CPUs

Database as a Service offering with high compatibility to Microsoft SQL Server

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Secondary database models

Spatial DBMS
Time Series DBMS

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	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

aws.amazon.com/redshift

cloud.google.com/datastore

www.kinetica.com

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

victoriametrics.com

Technical documentation

docs.aws.amazon.com/redshift

cloud.google.com/datastore/docs

docs.kinetica.com

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

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Amazon (based on PostgreSQL)

Google

Kinetica

Microsoft

VictoriaMetrics

Initial release

2012

2008

2012

2010

2018

Current release

7.1, August 2021

V12

v1.91, May 2023

License

Commercial or Open Source

commercial

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

C++

Server operating systems

hosted

Linux

hosted

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

user defined functions

in Python

using Google App Engine

user defined functions

Transact SQL

Triggers

Callbacks using the Google Apps Engine

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

Source-replica replication

yes, with always 3 replicas available

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users and roles on table level

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.