DBMS > Amazon Redshift vs. FatDB vs. IBM Db2 warehouse vs. NSDb

System Properties Comparison Amazon Redshift vs. FatDB vs. IBM Db2 warehouse vs. NSDb

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

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

Cloud-based data warehousing service

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Time Series DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.37
Rank	#160	Overall
	#74	Relational DBMS

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Website

aws.amazon.com/redshift

www.ibm.com/products/db2/warehouse

nsdb.io

Technical documentation

docs.aws.amazon.com/redshift

nsdb.io/Architecture

Developer

Amazon (based on PostgreSQL)

FatCloud

IBM

Initial release

2012

2014

2017

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

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, Scala

Server operating systems

hosted

Windows

hosted

Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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.

Import/export of XML data possible

Secondary indexes

restricted

yes

all fields are automatically indexed

SQL

Support of SQL

yes

does not fully support an SQL-standard

Via inetgration in SQL Server

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC

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

.NET Client API
JDBC
ODBC
OLE DB

gRPC
HTTP REST
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

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

Java
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

yes

via applications

PL/SQL, SQL PL

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

yes

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
Immediate Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

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

Using Apache Lucene

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

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

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.