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

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

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

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

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

Distributed, high-performance timeseries database

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Key-value store
Relational DBMS

Time Series 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

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Website

aws.amazon.com/redshift

druid.apache.org

www.gridgain.com

quasar.ai

Technical documentation

docs.aws.amazon.com/redshift

druid.apache.org/docs/latest/design

www.gridgain.com/docs/index.html

doc.quasar.ai/master

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation and contributors

GridGain Systems, Inc.

quasardb

Initial release

2012

2007

2009

Current release

29.0.1, April 2024

GridGain 8.5.1

3.14.1, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache license v2

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

Java, C++, .Net

C++

Server operating systems

hosted

Linux
OS X
Unix

Linux
OS X
Solaris
Windows

BSD
Linux
OS X
Windows

Data scheme

yes

schema-less columns are supported

yes

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL for querying

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

SQL-like query language

APIs and other access methods

JDBC
ODBC

JDBC
RESTful HTTP/JSON API

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

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

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

Triggers

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HDFS, S3 or other storage engines

yes (replicated cache)

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

In-memory capabilities

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

yes

Transient mode

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

Security Hooks for custom implementations

Cryptographically strong user authentication and audit trail

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.