DBMS > Amazon Redshift vs. HEAVY.AI vs. IBM Cloudant vs. OpenQM vs. TimescaleDB

System Properties Comparison Amazon Redshift vs. HEAVY.AI vs. IBM Cloudant vs. OpenQM vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Database as a Service offering based on Apache CouchDB

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

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

aws.amazon.com/redshift

github.com/heavyai/heavydb
www.heavy.ai

www.ibm.com/products/cloudant

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

www.timescale.com

Technical documentation

docs.aws.amazon.com/redshift

docs.heavy.ai

cloud.ibm.com/docs/Cloudant

docs.timescale.com

Developer

Amazon (based on PostgreSQL)

HEAVY.AI, Inc.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Rocket Software, originally Martin Phillips

Timescale

Initial release

2012

2016

2010

1993

2017

Current release

5.10, January 2022

3.4-12

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

commercial

Open Source

GPLv2, extended commercial license available

Open Source

Apache 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++ and CUDA

Erlang

Server operating systems

hosted

Linux

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

with some exceptions

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data 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.

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

full PostgreSQL SQL syntax

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Thrift
Vega

RESTful HTTP/JSON API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/Thrift
Python

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
Basic
C
Java
Objective C
PHP
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

View functions (Map-Reduce) in JavaScript

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

yes

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Multi-source replication
Source-replica replication

yes

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate 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

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Access rights for users can be defined per database

Access rights can be defined down to the item 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.