DBMS > Amazon Redshift vs. Apache Druid vs. Drizzle vs. GridGain

System Properties Comparison Amazon Redshift vs. Apache Druid vs. Drizzle vs. GridGain

Please select another system to include it in the comparison.

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

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

GridGain is an in-memory computing platform, built on Apache Ignite

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Relational DBMS

Key-value 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	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Website

aws.amazon.com/redshift

druid.apache.org

www.gridgain.com

Technical documentation

docs.aws.amazon.com/redshift

druid.apache.org/docs/latest/design

www.gridgain.com/docs/index.html

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation and contributors

Drizzle project, originally started by Brian Aker

GridGain Systems, Inc.

Initial release

2012

2008

2007

Current release

29.0.1, April 2024

7.2.4, September 2012

GridGain 8.5.1

License

Commercial or Open Source

commercial

Open Source

Apache license v2

Open Source

GNU GPL

commercial

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

Java, C++, .Net

Server operating systems

hosted

Linux
OS X
Unix

FreeBSD
Linux
OS X

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-less columns are supported

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.

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL for querying

yes

with proprietary extensions

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

JDBC
ODBC

JDBC
RESTful HTTP/JSON API

JDBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C
C++
Java
PHP

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

yes (compute grid and cache interceptors can be used instead)

Triggers

hooks for callbacks inside the server can be used.

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HDFS, S3 or other storage engines

Multi-source replication
Source-replica replication

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate 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

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Security Hooks for custom implementations

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.