DBMS > Amazon Redshift vs. Apache IoTDB vs. FatDB vs. PouchDB

System Properties Comparison Amazon Redshift vs. Apache IoTDB vs. FatDB vs. PouchDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

Large scale data warehouse service for use with business intelligence tools

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Relational DBMS

Time Series DBMS

Document store
Key-value store

Document store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

aws.amazon.com/redshift

iotdb.apache.org

pouchdb.com

Technical documentation

docs.aws.amazon.com/redshift

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

pouchdb.com/guides

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

FatCloud

Apache Software Foundation

Initial release

2012

2018

2012

Current release

1.1.0, April 2023

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

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

JavaScript

Server operating systems

hosted

All OS with a Java VM (>= 1.8)

Windows

server-less, requires a JavaScript environment (browser, Node.js)

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

via views

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

Via inetgration in SQL Server

APIs and other access methods

JDBC
ODBC

JDBC
Native API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Go
Java
Python
Scala

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

yes

via applications

View functions in JavaScript

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

selectable replication factor

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong Consistency with Raft

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

by using IndexedDB, WebSQL or LevelDB as backend

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

Can implement custom security layer via applications

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.