DBMS > Amazon Redshift vs. EXASOL vs. STSdb vs. SwayDB

System Properties Comparison Amazon Redshift vs. EXASOL vs. STSdb vs. SwayDB

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

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

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

Primary database model

Relational DBMS

Key-value store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

aws.amazon.com/redshift

www.exasol.com

github.com/STSSoft/STSdb4

swaydb.simer.au

Technical documentation

docs.aws.amazon.com/redshift

www.exasol.com/resources

Developer

Amazon (based on PostgreSQL)

Exasol

STS Soft SC

Simer Plaha

Initial release

2012

2000

2011

2018

Current release

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

GPLv2, commercial license 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

Scala

Server operating systems

hosted

Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

APIs and other access methods

JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

.NET Client API

Supported programming languages

All languages supporting JDBC/ODBC

Java
Lua
Python
R

C#
Java

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

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

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

Access rights for users, groups and roles 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.