DBMS > Amazon Redshift vs. HEAVY.AI vs. IBM Db2 warehouse vs. Kinetica vs. Quasardb

System Properties Comparison Amazon Redshift vs. HEAVY.AI vs. IBM Db2 warehouse vs. Kinetica vs. Quasardb

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

Cloud-based data warehousing service

Fully vectorized database across both GPUs and CPUs

Distributed, high-performance timeseries database

Primary database model

Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

Spatial DBMS
Time Series DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	1.37
Rank	#160	Overall
	#74	Relational DBMS

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Website

aws.amazon.com/redshift

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

www.ibm.com/products/db2/warehouse

www.kinetica.com

quasar.ai

Technical documentation

docs.aws.amazon.com/redshift

docs.heavy.ai

docs.kinetica.com

doc.quasar.ai/master

Developer

Amazon (based on PostgreSQL)

HEAVY.AI, Inc.

IBM

Kinetica

quasardb

Initial release

2012

2016

2014

2012

2009

Current release

5.10, January 2022

7.1, August 2021

3.14.1, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

C, C++

C++

Server operating systems

hosted

Linux

hosted

Linux

BSD
Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

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.

Import/export of XML data possible

Secondary indexes

restricted

yes

with tags

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like DML and DDL statements

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Thrift
Vega

.NET Client API
JDBC
ODBC
OLE DB

JDBC
ODBC
RESTful HTTP API

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/Thrift
Python

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

C++
Java
JavaScript (Node.js)
Python

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

PL/SQL, SQL PL

user defined functions

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes

Source-replica replication

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

GPU vRAM or System RAM

yes

Transient mode

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

Cryptographically strong user authentication and audit trail

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.