DBMS > Amazon Redshift vs. Drizzle vs. EXASOL vs. GigaSpaces

System Properties Comparison Amazon Redshift vs. Drizzle vs. EXASOL vs. GigaSpaces

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

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Values are user defined objects

Secondary database models

Graph DBMS
Search engine

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	1.03
Rank	#188	Overall
	#32	Document stores
	#6	Object oriented DBMS

Website

aws.amazon.com/redshift

www.exasol.com

www.gigaspaces.com

Technical documentation

docs.aws.amazon.com/redshift

www.exasol.com/resources

docs.gigaspaces.com/latest/landing.html

Developer

Amazon (based on PostgreSQL)

Drizzle project, originally started by Brian Aker

Exasol

Gigaspaces Technologies

Initial release

2012

2008

2000

Current release

7.2.4, September 2012

15.5, September 2020

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

Open Source

Apache Version 2; Commercial licenses 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++

Java, C++, .Net

Server operating systems

hosted

FreeBSD
Linux
OS X

Linux
macOS
Solaris
Windows

Data scheme

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.

XML can be used for describing objects metadata

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

yes

SQL-99 for query and DML statements

APIs and other access methods

JDBC
ODBC

JDBC

.Net
JDBC
ODBC
WebSocket

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

Java
Lua
Python
R

.Net
C++
Java
Python
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

Triggers

hooks for callbacks inside the server can be used.

yes

yes, event driven architecture

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

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users, groups and roles according to SQL-standard

Role-based access control

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.