DBMS > Amazon Redshift vs. BaseX vs. Riak KV vs. STSdb

System Properties Comparison Amazon Redshift vs. BaseX vs. Riak KV vs. STSdb

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

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

Distributed, fault tolerant key-value store

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

Native XML DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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	1.90
Rank	#136	Overall
	#4	Native XML DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Score	0.06
Rank	#365	Overall
	#55	Key-value stores

Website

aws.amazon.com/redshift

basex.org

github.com/STSSoft/STSdb4

Technical documentation

docs.aws.amazon.com/redshift

docs.basex.org

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

Developer

Amazon (based on PostgreSQL)

BaseX GmbH

OpenSource, formerly Basho Technologies

STS Soft SC

Initial release

2012

2007

2009

2011

Current release

10.7, August 2023

3.2.0, December 2022

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

BSD license

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPLv2, commercial license available

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

Linux
OS X
Windows

Linux
OS X

Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

XQuery supports types

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

restricted

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

HTTP API
Native Erlang Interface

.NET Client API

Supported programming languages

All languages supporting JDBC/ODBC

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

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

C#
Java

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Erlang

Triggers

yes

via events

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

selectable replication factor

none

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

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

links between data sets can be stored

Transaction concepts

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

ACID

multiple readers, single writer

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

Users with fine-grained authorization concept on 4 levels

yes, using Riak Security

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.