DBMS > Amazon Redshift vs. CrateDB vs. Riak TS vs. Transwarp ArgoDB

System Properties Comparison Amazon Redshift vs. CrateDB vs. Riak TS vs. Transwarp ArgoDB

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

Distributed Database based on Lucene

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Distributed Analytical Database to replace Hadoop+MPP hybrid architecture

Primary database model

Relational DBMS

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Relational DBMS

Search engine

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	0.69
Rank	#226	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#11	Vector DBMS

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Score	0.04
Rank	#361	Overall
	#153	Relational DBMS

Website

aws.amazon.com/redshift

cratedb.com

www.transwarp.cn/en/product/argodb

Technical documentation

docs.aws.amazon.com/redshift

cratedb.com/docs

www.tiot.jp/riak-docs/riak/ts/latest

docs.transwarp.cn/#/documents-support/docs?category=ARGODB

Developer

Amazon (based on PostgreSQL)

Crate

Open Source, formerly Basho Technologies

Transwarp

Initial release

2012

2013

2015

Current release

5.8.1, August 2024

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

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

Erlang

Server operating systems

hosted

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

Linux
OS X

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

schema-free

yes

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes, but no triggers and constraints, and PostgreSQL compatibility

yes, limited

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions (Javascript)

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Configurable replication on table/partition-level

selectable replication factor

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
Read-after-write consistency on record level

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

links between datasets can be stored

Transaction concepts

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

ACID

unique row identifiers can be used for implementing an optimistic concurrency control strategy

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

rights management via user accounts

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.