DBMS > Amazon Redshift vs. Coveo vs. Heroic vs. Microsoft Azure Synapse Analytics vs. VoltDB

System Properties Comparison Amazon Redshift vs. Coveo vs. Heroic vs. Microsoft Azure Synapse Analytics vs. VoltDB

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	19.93
Rank	#31	Overall
	#19	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

aws.amazon.com/redshift

www.coveo.com

github.com/spotify/heroic

azure.microsoft.com/services/synapse-analytics

www.voltdb.com

Technical documentation

docs.aws.amazon.com/redshift

docs.coveo.com

spotify.github.io/heroic

docs.microsoft.com/azure/synapse-analytics

docs.voltdb.com

Developer

Amazon (based on PostgreSQL)

Coveo

Spotify

Microsoft

VoltDB Inc.

Initial release

2012

2014

2016

2010

Current release

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java

C++

Java, C++

Server operating systems

hosted

Linux
OS X

for development

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

yes

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.

Secondary indexes

restricted

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Python

C#
Java
PHP

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Transact SQL

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

yes

Users and roles with access to stored procedures

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.