DBMS > Amazon Redshift vs. Microsoft Azure Cosmos DB vs. VictoriaMetrics vs. XTDB

System Properties Comparison Amazon Redshift vs. Microsoft Azure Cosmos DB vs. VictoriaMetrics vs. XTDB

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

Globally distributed, horizontally scalable, multi-model database service

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Document store

Secondary database models

Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

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

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

aws.amazon.com/redshift

azure.microsoft.com/services/cosmos-db

victoriametrics.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.aws.amazon.com/redshift

learn.microsoft.com/azure/cosmos-db

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

www.xtdb.com/docs

Developer

Amazon (based on PostgreSQL)

Microsoft

VictoriaMetrics

Juxt Ltd.

Initial release

2012

2014

2018

2019

Current release

v1.91, May 2023

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

MIT License

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

Clojure

Server operating systems

hosted

FreeBSD
Linux
macOS
OpenBSD

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes, extensible-data-notation format

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.

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 query language

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

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

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

HTTP REST
JDBC

Supported programming languages

All languages supporting JDBC/ODBC

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

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in Python

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Synchronous replication

yes, each node contains all data

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Access rights can be defined down to the item level

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.