DBMS > Amazon Redshift vs. Datomic vs. Drizzle vs. RethinkDB vs. SwayDB

System Properties Comparison Amazon Redshift vs. Datomic vs. Drizzle vs. RethinkDB 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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

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

Primary database model

Relational DBMS

Document store

Key-value store

Secondary database models

Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	2.74
Rank	#105	Overall
	#19	Document stores

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

Website

aws.amazon.com/redshift

www.datomic.com

rethinkdb.com

swaydb.simer.au

Technical documentation

docs.aws.amazon.com/redshift

docs.datomic.com

rethinkdb.com/docs

Developer

Amazon (based on PostgreSQL)

Cognitect

Drizzle project, originally started by Brian Aker

The Linux Foundation

since July 2017

Simer Plaha

Initial release

2012

2008

2009

2018

Current release

1.0.6735, June 2023

7.2.4, September 2012

2.4.1, August 2020

License

Commercial or Open Source

commercial

limited edition free

Open Source

GNU GPL

Open Source

Apache Version 2

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

Java, Clojure

C++

Scala

Server operating systems

hosted

All OS with a Java VM

FreeBSD
Linux
OS X

Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

JDBC

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

C
C++
Java
PHP

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

Triggers

By using transaction functions

hooks for callbacks inside the server can be used.

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

range based

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

Multi-source replication
Source-replica replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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 single-document operations

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

users and table-level permissions

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.