DBMS > Amazon Redshift vs. BaseX vs. Drizzle vs. HEAVY.AI vs. mSQL

System Properties Comparison Amazon Redshift vs. BaseX vs. Drizzle vs. HEAVY.AI vs. mSQL

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

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

Primary database model

Relational DBMS

Native XML DBMS

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.84
Rank	#135	Overall
	#4	Native XML DBMS

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Website

aws.amazon.com/redshift

basex.org

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

hughestech.com.au/products/msql

Technical documentation

docs.aws.amazon.com/redshift

docs.basex.org

docs.heavy.ai

Developer

Amazon (based on PostgreSQL)

BaseX GmbH

Drizzle project, originally started by Brian Aker

HEAVY.AI, Inc.

Hughes Technologies

Initial release

2012

2007

2008

2016

1994

Current release

10.7, August 2023

7.2.4, September 2012

5.10, January 2022

4.4, October 2021

License

Commercial or Open Source

commercial

Open Source

BSD license

Open Source

GNU GPL

Open Source

Apache Version 2; enterprise edition available

commercial

free licenses can be provided

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

Java

C++

C++ and CUDA

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
OS X

Linux

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

XQuery supports types

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

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

JDBC

JDBC
ODBC
Thrift
Vega

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

C
C++
Java
PHP

All languages supporting JDBC/ODBC/Thrift
Python

C
C++
Delphi
Java
Perl
PHP
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

via events

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Round robin

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

multiple readers, single writer

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

Users with fine-grained authorization concept on 4 levels

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.