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

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

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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Relational DBMS

Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

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	2.28
Rank	#114	Overall
	#11	Search engines

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

Website

aws.amazon.com/redshift

www.coveo.com

azure.microsoft.com/services/cosmos-db

victoriametrics.com

Technical documentation

docs.aws.amazon.com/redshift

docs.coveo.com

learn.microsoft.com/azure/cosmos-db

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

Developer

Amazon (based on PostgreSQL)

Coveo

Microsoft

VictoriaMetrics

Initial release

2012

2014

2018

Current release

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

Server operating systems

hosted

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

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

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Python

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

Server-side scripts

Stored procedures

user defined functions

in Python

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Synchronous 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

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

yes

Transaction concepts

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

ACID

yes

Multi-item ACID transactions with snapshot isolation within a partition

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

User concepts

Access control

fine grained access rights according to SQL-standard

granular access controls, API key management, content filters

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.