DBMS > Amazon DocumentDB vs. Amazon Redshift vs. IBM Cloudant vs. RRDtool

System Properties Comparison Amazon DocumentDB vs. Amazon Redshift vs. IBM Cloudant vs. RRDtool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Large scale data warehouse service for use with business intelligence tools

Database as a Service offering based on Apache CouchDB

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Primary database model

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Website

aws.amazon.com/documentdb

aws.amazon.com/redshift

www.ibm.com/products/cloudant

oss.oetiker.ch/rrdtool

Technical documentation

aws.amazon.com/documentdb/resources

docs.aws.amazon.com/redshift

cloud.ibm.com/docs/Cloudant

oss.oetiker.ch/rrdtool/doc

Developer

Amazon (based on PostgreSQL)

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Tobias Oetiker

Initial release

2019

2012

2010

1999

Current release

1.8.0, 2022

License

Commercial or Open Source

commercial

Open Source

GPL V2 and FLOSS

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

Erlang

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

hosted

HP-UX
Linux

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Exporting into and restoring from XML files possible

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
ODBC

RESTful HTTP/JSON API

in-process shared library
Pipes

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Objective-C
PHP
Ruby

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

none

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

informational only, not enforced by the system

Transaction concepts

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

Atomic single-document operations

ACID

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

by using the rrdcached daemon

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

Access rights for users and roles

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

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.