DBMS > Amazon Redshift vs. RethinkDB vs. Vitess vs. XTDB

System Properties Comparison Amazon Redshift vs. RethinkDB vs. Vitess vs. XTDB

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

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

Scalable, distributed, cloud-native DBMS, extending MySQL

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.66
Rank	#107	Overall
	#20	Document stores

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

aws.amazon.com/redshift

rethinkdb.com

vitess.io

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.aws.amazon.com/redshift

rethinkdb.com/docs

vitess.io/docs

www.xtdb.com/docs

Developer

Amazon (based on PostgreSQL)

The Linux Foundation

since July 2017

The Linux Foundation, PlanetScale

Juxt Ltd.

Initial release

2012

2009

2013

2019

Current release

2.4.1, August 2020

15.0.2, December 2022

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache Version 2.0, commercial licenses available

Open Source

MIT License

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

Clojure

Server operating systems

hosted

Linux
OS X
Windows

Docker
Linux
macOS

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

yes

yes, extensible-data-notation format

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

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP REST
JDBC

Supported programming languages

All languages supporting JDBC/ODBC

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

proprietary syntax

Triggers

Client-side triggers through changefeeds

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

range based

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication
Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

not for MyISAM storage engine

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Atomic single-document operations

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

yes

users and table-level permissions

Users with fine-grained authorization concept

no user groups or roles

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.