DBMS > Amazon Redshift vs. Heroic vs. Microsoft Azure AI Search vs. OpenQM

System Properties Comparison Amazon Redshift vs. Heroic vs. Microsoft Azure AI Search vs. OpenQM

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

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

Search-as-a-service for web and mobile app development

QpenQM is a high-performance, self-tuning, multi-value DBMS

Primary database model

Secondary database models

Vector DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Website

aws.amazon.com/redshift

github.com/spotify/heroic

azure.microsoft.com/en-us/services/search

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

Technical documentation

docs.aws.amazon.com/redshift

spotify.github.io/heroic

learn.microsoft.com/en-us/azure/search

Developer

Amazon (based on PostgreSQL)

Spotify

Microsoft

Rocket Software, originally Martin Phillips

Initial release

2012

2014

2015

1993

Current release

3.4-12

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

GPLv2, extended 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

Java

Server operating systems

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

yes

schema-free

yes

with some exceptions

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.

yes

Secondary indexes

restricted

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

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

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Python

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

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

Transaction concepts

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

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

User concepts

Access control

fine grained access rights according to SQL-standard

yes

using Azure authentication

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.