DBMS > Amazon Redshift vs. Apache Drill vs. Drizzle vs. EsgynDB vs. Geode

System Properties Comparison Amazon Redshift vs. Apache Drill vs. Drizzle vs. EsgynDB vs. Geode

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

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Primary database model

Relational DBMS

Document store
Relational DBMS

Relational DBMS

Key-value store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Website

aws.amazon.com/redshift

drill.apache.org

www.esgyn.cn

geode.apache.org

Technical documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

geode.apache.org/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Drizzle project, originally started by Brian Aker

Esgyn

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Initial release

2012

2008

2015

2002

Current release

1.20.3, January 2023

7.2.4, September 2012

1.1, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

GNU GPL

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Java

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
OS X

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Data scheme

yes

schema-free

yes

schema-free

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

yes

with proprietary extensions

yes

SQL-like query language (OQL)

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

JDBC

ADO.NET
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C++

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

.Net
All JVM based languages
C++
Groovy
Java
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Java Stored Procedures

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

Multi-source 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

Eventual 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

yes, on a single node

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

Access rights per client and object definable

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.