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

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

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

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

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.

Primary database model

Relational DBMS

Document store
Relational DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	4.13
Rank	#80	Overall
	#6	Time Series DBMS

Website

aws.amazon.com/redshift

drill.apache.org

iotdb.apache.org

www.dolphindb.com

Technical documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

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

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

DolphinDB, Inc

Initial release

2012

2018

Current release

1.20.3, January 2023

1.1.0, April 2023

v2.00.4, January 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache Version 2.0

commercial

free community version 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

Java

C++

Server operating systems

hosted

Linux
OS X
Windows

All OS with a Java VM (>= 1.8)

Linux
Windows

Data scheme

yes

schema-free

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

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

JDBC
Native API

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

Supported programming languages

All languages supporting JDBC/ODBC

C++

C
C#
C++
Go
Java
Python
Scala

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

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Integration with Hadoop and Spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency
Strong Consistency with Raft

Immediate 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

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

yes

Administrators, Users, Groups

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.