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

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

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

A high-performance vector database with neural network or semantic-based matching

Primary database model

Relational DBMS

Vector DBMS

Secondary database models

Spatial 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	1.53
Rank	#145	Overall
	#7	Vector DBMS

Website

aws.amazon.com/redshift

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

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

docs.aws.amazon.com/redshift

docs.heavy.ai

qdrant.tech/documentation

Developer

Amazon (based on PostgreSQL)

Drizzle project, originally started by Brian Aker

HEAVY.AI, Inc.

Qdrant

Initial release

2012

2008

2016

2021

Current release

7.2.4, September 2012

5.10, January 2022

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

Apache Version 2; enterprise edition available

Open Source

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

C++ and CUDA

Rust

Server operating systems

hosted

FreeBSD
Linux
OS X

Linux

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC

JDBC

JDBC
ODBC
Thrift
Vega

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

All languages supporting JDBC/ODBC/Thrift
Python

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency, tunable 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

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

Key-based authentication

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.