DBMS > Amazon Redshift vs. Drizzle vs. HEAVY.AI vs. SingleStore

System Properties Comparison Amazon Redshift vs. Drizzle vs. HEAVY.AI vs. SingleStore

Please select another system to include it in the comparison.

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

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Primary database model

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	1.41
Rank	#153	Overall
	#71	Relational DBMS

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Website

aws.amazon.com/redshift

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

www.singlestore.com

Technical documentation

docs.aws.amazon.com/redshift

docs.heavy.ai

docs.singlestore.com

Developer

Amazon (based on PostgreSQL)

Drizzle project, originally started by Brian Aker

HEAVY.AI, Inc.

SingleStore Inc.

Initial release

2012

2008

2016

2013

Current release

7.2.4, September 2012

5.10, January 2022

8.5, January 2024

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

Apache Version 2; enterprise edition available

commercial

free developer 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

C++, Go

Server operating systems

hosted

FreeBSD
Linux
OS X

Linux

64 bit version required

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

yes

with proprietary extensions

yes

but no triggers and foreign keys

APIs and other access methods

JDBC
ODBC

JDBC

JDBC
ODBC
Thrift
Vega

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

All languages supporting JDBC/ODBC/Thrift
Python

Bash
C
C#
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

hash partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication

Source-replica replication

stores two copies of each physical data partition on two separate nodes

MapReduce

Offers an API for user-defined Map/Reduce methods

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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

fine grained access rights according to SQL-standard

Fine grained access control via users, groups and roles

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.