DBMS > Amazon Redshift vs. Apache Druid vs. EXASOL vs. FatDB

System Properties Comparison Amazon Redshift vs. Apache Druid vs. EXASOL vs. FatDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the 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

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Relational DBMS

Document store
Key-value store

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	3.29
Rank	#95	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

Score	2.25
Rank	#120	Overall
	#57	Relational DBMS

Website

aws.amazon.com/redshift

druid.apache.org

www.exasol.com

Technical documentation

docs.aws.amazon.com/redshift

druid.apache.org/docs/latest/design

www.exasol.com/resources

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation and contributors

Exasol

FatCloud

Initial release

2012

2000

2012

Current release

29.0.1, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache license v2

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

Server operating systems

hosted

Linux
OS X
Unix

Windows

Data scheme

yes

schema-less columns are supported

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 for querying

yes

Via inetgration in SQL Server

APIs and other access methods

JDBC
ODBC

JDBC
RESTful HTTP/JSON API

.Net
JDBC
ODBC
WebSocket

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Java
Lua
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

via applications

Triggers

yes

via applications

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

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

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

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

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

Can implement custom security layer via applications

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.