DBMS > Amazon Redshift vs. Apache Drill vs. DolphinDB vs. HBase

System Properties Comparison Amazon Redshift vs. Apache Drill vs. DolphinDB vs. HBase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

Wide-column store based on Apache Hadoop and on concepts of BigTable

Primary database model

Relational DBMS

Document store
Relational DBMS

Time Series DBMS

Wide column store

Secondary database models

Relational DBMS

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	4.23
Rank	#82	Overall
	#6	Time Series DBMS

Score	31.25
Rank	#26	Overall
	#2	Wide column stores

Website

aws.amazon.com/redshift

drill.apache.org

www.dolphindb.com

hbase.apache.org

Technical documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

docs.dolphindb.cn/en/help200/index.html

hbase.apache.org/book.html

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

DolphinDB, Inc

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Initial release

2012

2018

2008

Current release

1.20.3, January 2023

v2.00.4, January 2022

2.3.4, January 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

free community version available

Open Source

Apache version 2

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

Java

Server operating systems

hosted

Linux
OS X
Windows

Linux
Windows

Linux
Unix
Windows

using Cygwin

Data scheme

yes

schema-free

yes

schema-free, schema definition possible

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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 SELECT statement is SQL:2003 compliant

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

JDBC
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

Java API
RESTful HTTP API
Thrift

Supported programming languages

All languages supporting JDBC/ODBC

C++

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

C
C#
C++
Groovy
Java
PHP
Python
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

Coprocessors in Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Immediate Consistency or Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

yes

Single row ACID (across millions of columns)

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Depending on the underlying data source

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Depending on the underlying data source

Administrators, Users, Groups

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.