DBMS > Amazon Redshift vs. FatDB vs. IBM Cloudant vs. QuestDB vs. SiriDB

System Properties Comparison Amazon Redshift vs. FatDB vs. IBM Cloudant vs. QuestDB vs. SiriDB

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.

Database as a Service offering based on Apache CouchDB

A high performance open source SQL database for time series data

Open Source Time Series DBMS

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	2.52
Rank	#109	Overall
	#9	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

aws.amazon.com/redshift

www.ibm.com/products/cloudant

questdb.io

siridb.com

Technical documentation

docs.aws.amazon.com/redshift

cloud.ibm.com/docs/Cloudant

questdb.io/docs

docs.siridb.com

Developer

Amazon (based on PostgreSQL)

FatCloud

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

QuestDB Technology Inc

Cesbit

Initial release

2012

2010

2014

2017

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

MIT License

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

Java (Zero-GC), C++, Rust

Server operating systems

hosted

Windows

hosted

Linux
macOS
Windows

Linux

Data scheme

yes

schema-free

yes

schema-free via InfluxDB Line Protocol

yes

Typing

predefined data types such as float or date

yes

Numeric data

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

Via inetgration in SQL Server

SQL with time-series extensions

APIs and other access methods

JDBC
ODBC

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

RESTful HTTP/JSON API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Objective-C
PHP
Ruby

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes

via applications

View functions (Map-Reduce) in JavaScript

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by timestamps)

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Multi-source replication
Source-replica replication

Source-replica replication with eventual consistency

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

Eventual Consistency

Immediate 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

atomic operations within a document possible

ACID for single-table writes

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

through memory mapped files

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

Access rights for users can be defined per database

simple rights management via user accounts

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

QuestDB and Raspberry Pi 5 benchmark, a pocket-sized powerhouse
8 May 2024

Build your own resource monitor with QuestDB and Grafana
6 May 2024

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

Create an ADS-B flight radar with QuestDB and a Raspberry Pi
8 April 2024

Build a temperature IoT sensor with Raspberry Pi Pico & QuestDB
5 April 2024

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.