DBMS > Amazon Redshift vs. Apache Drill vs. Dragonfly vs. YDB

System Properties Comparison Amazon Redshift vs. Apache Drill vs. Dragonfly vs. YDB

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

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Relational DBMS

Document store
Relational DBMS

Key-value store

Document store
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	0.41
Rank	#266	Overall
	#38	Key-value stores

Score	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Website

aws.amazon.com/redshift

drill.apache.org

github.com/dragonflydb/dragonfly
www.dragonflydb.io

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

www.dragonflydb.io/docs

ydb.tech/en/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

DragonflyDB team and community contributors

Yandex

Initial release

2012

2023

2019

Current release

1.20.3, January 2023

1.0, March 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

BSL 1.1

Open Source

Apache 2.0; commercial license 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++

Server operating systems

hosted

Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

scheme-free

Flexible Schema (defined schema, partial schema, schema free)

Typing

predefined data types such as float or date

yes

strings, hashes, lists, sets, sorted sets, bit arrays

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 (YQL)

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

Proprietary protocol

RESP - REdis Serialization Protocol

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

All languages supporting JDBC/ODBC

C++

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Lua

Triggers

publish/subscribe channels provide some trigger functionality

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Active-passive shard 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

Eventual Consistency

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

Atomic execution of command blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, strict serializability by the server

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

Password-based authentication

Access rights defined for Yandex Cloud users

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.