DBMS > Amazon Redshift vs. Drizzle vs. HEAVY.AI vs. Ingres vs. Kinetica

System Properties Comparison Amazon Redshift vs. Drizzle vs. HEAVY.AI vs. Ingres vs. Kinetica

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

Well established RDBMS

Fully vectorized database across both GPUs and CPUs

Primary database model

Relational DBMS

Secondary database models

Spatial DBMS

Spatial DBMS
Time Series 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	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Website

aws.amazon.com/redshift

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

www.actian.com/databases/ingres

www.kinetica.com

Technical documentation

docs.aws.amazon.com/redshift

docs.heavy.ai

docs.actian.com/ingres

docs.kinetica.com

Developer

Amazon (based on PostgreSQL)

Drizzle project, originally started by Brian Aker

HEAVY.AI, Inc.

Actian Corporation

Kinetica

Initial release

2012

2008

2016

1974

originally developed at University Berkely in early 1970s

2012

Current release

7.2.4, September 2012

5.10, January 2022

11.2, May 2022

7.1, August 2021

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

Apache Version 2; enterprise edition available

commercial

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++

C++ and CUDA

C, C++

Server operating systems

hosted

FreeBSD
Linux
OS X

Linux

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

yes

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

JDBC

JDBC
ODBC
Thrift
Vega

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

JDBC
ODBC
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

All languages supporting JDBC/ODBC/Thrift
Python

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions

Triggers

hooks for callbacks inside the server can be used.

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

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication

Ingres Replicator

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

Immediate Consistency or Eventual Consistency depending on configuration

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

MVCC

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

GPU vRAM or System RAM

User concepts

Access control

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

Access rights for users and roles on table 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.