DBMS > Amazon Redshift vs. Drizzle vs. EXASOL vs. IBM Db2 Event Store vs. SwayDB

System Properties Comparison Amazon Redshift vs. Drizzle vs. EXASOL vs. IBM Db2 Event Store vs. SwayDB

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.

Distributed Event Store optimized for Internet of Things use cases

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Relational DBMS

Event Store
Time Series 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	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	0.27
Rank	#309	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

aws.amazon.com/redshift

www.exasol.com

www.ibm.com/products/db2-event-store

swaydb.simer.au

Technical documentation

docs.aws.amazon.com/redshift

www.exasol.com/resources

www.ibm.com/docs/en/db2-event-store

Developer

Amazon (based on PostgreSQL)

Drizzle project, originally started by Brian Aker

Exasol

IBM

Simer Plaha

Initial release

2012

2008

2000

2017

2018

Current release

7.2.4, September 2012

2.0

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

free developer edition available

Open Source

GNU Affero GPL V3.0

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

Scala

Server operating systems

hosted

FreeBSD
Linux
OS X

Linux

Linux, macOS, Windows for the developer addition

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

yes

through the embedded Spark runtime

APIs and other access methods

JDBC
ODBC

JDBC

.Net
JDBC
ODBC
WebSocket

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

Java
Lua
Python
R

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

Java
Kotlin
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

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Active-active shard replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

yes

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

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

fine grained access rights according to SQL-standard

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.