DBMS > Amazon Redshift vs. IBM Cloudant vs. SAP Advantage Database Server vs. Tarantool vs. TimescaleDB

System Properties Comparison Amazon Redshift vs. IBM Cloudant vs. SAP Advantage Database Server vs. Tarantool vs. TimescaleDB

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Database as a Service offering based on Apache CouchDB

Low-cost RDBMS with access to ISAM and FoxPro data structures

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS

Document store

Relational DBMS

Document store
Key-value store
Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

aws.amazon.com/redshift

www.ibm.com/products/cloudant

www.sap.com/products/advantage-database-server.html

www.tarantool.io

www.timescale.com

Technical documentation

docs.aws.amazon.com/redshift

cloud.ibm.com/docs/Cloudant

www.tarantool.io/en/doc

docs.timescale.com

Developer

Amazon (based on PostgreSQL)

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Sybase, SAP

Timescale

Initial release

2012

2010

1993

2008

2017

Current release

2.10.0, May 2022

2.13.0, November 2023

License

Commercial or Open Source

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Open Source

Apache 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

Erlang

C and C++

Server operating systems

hosted

Linux
Windows

BSD
Linux
macOS

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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.

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

Full-featured ANSI SQL support

yes

full PostgreSQL SQL syntax

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Open binary protocol

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Objective-C
PHP
Ruby

Delphi
Perl
PHP

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

View functions (Map-Reduce) in JavaScript

yes

Lua, C and SQL stored procedures

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

yes, before/after data modification events, on replication events, client session events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

Source-replica replication with hot standby and reads on replicas

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

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Immediate 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

atomic operations within a document possible

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

caching of (temporary) tables can be configured

yes, full featured in-memory storage engine with persistence

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.