DBMS > Amazon Redshift vs. BigObject vs. Drizzle vs. EXASOL vs. HEAVY.AI

System Properties Comparison Amazon Redshift vs. BigObject vs. Drizzle vs. EXASOL vs. HEAVY.AI

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

Analytic DBMS for real-time computations and queries

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Website

aws.amazon.com/redshift

bigobject.io

www.exasol.com

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

Technical documentation

docs.aws.amazon.com/redshift

docs.bigobject.io

www.exasol.com/resources

docs.heavy.ai

Developer

Amazon (based on PostgreSQL)

BigObject, Inc.

Drizzle project, originally started by Brian Aker

Exasol

HEAVY.AI, Inc.

Initial release

2012

2015

2008

2000

2016

Current release

7.2.4, September 2012

5.10, January 2022

License

Commercial or Open Source

commercial

free community edition available

Open Source

GNU GPL

commercial

Open Source

Apache Version 2; enterprise edition 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

C++

C++ and CUDA

Server operating systems

hosted

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

FreeBSD
Linux
OS X

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC

fluentd
ODBC
RESTful HTTP API

JDBC

.Net
JDBC
ODBC
WebSocket

JDBC
ODBC
Thrift
Vega

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

Java
Lua
Python
R

All languages supporting JDBC/ODBC/Thrift
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Round robin

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users, groups and roles according to SQL-standard

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.