DBMS > Amazon Redshift vs. IBM Db2 vs. MonetDB vs. Riak KV

System Properties Comparison Amazon Redshift vs. IBM Db2 vs. MonetDB vs. Riak KV

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

Common in IBM host environments, 2 different versions for host and Windows/Linux

A relational database management system that stores data in columns

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Key-value store

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

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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	125.90
Rank	#9	Overall
	#6	Relational DBMS

Score	1.72
Rank	#141	Overall
	#64	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Website

aws.amazon.com/redshift

www.ibm.com/products/db2

www.monetdb.org

Technical documentation

docs.aws.amazon.com/redshift

www.ibm.com/docs/en/db2

www.monetdb.org/Documentation

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

Developer

Amazon (based on PostgreSQL)

IBM

MonetDB BV

OpenSource, formerly Basho Technologies

Initial release

2012

1983

host version

2004

2009

Current release

12.1, October 2016

Dec2023 (11.49), December 2023

3.2.0, December 2022

License

Commercial or Open Source

commercial

free version is available

Open Source

Mozilla Public License 2.0

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X

Data scheme

yes

schema-free

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL 2003 with some extensions

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

HTTP API
Native Erlang Interface

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

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

yes

yes, in SQL, C, R

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

Sharding via remote tables

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

none

Source-replica replication available in experimental status

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

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

links between data sets can be stored

Transaction concepts

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

ACID

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

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.