DBMS > Amazon Redshift vs. IBM Cloudant vs. Interbase vs. ToroDB vs. Warp 10

System Properties Comparison Amazon Redshift vs. IBM Cloudant vs. Interbase vs. ToroDB vs. Warp 10

Editorial information provided by DB-Engines

Name

ToroDB 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

Light-weight proven RDBMS

originally from Borland

A MongoDB-compatible JSON document store, built on top of PostgreSQL

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

aws.amazon.com/redshift

www.ibm.com/products/cloudant

www.embarcadero.com/products/interbase

github.com/torodb/server

www.warp10.io

Technical documentation

docs.aws.amazon.com/redshift

cloud.ibm.com/docs/Cloudant

docs.embarcadero.com/products/interbase

www.warp10.io/content/02_Getting_started

Developer

Amazon (based on PostgreSQL)

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Embarcadero

8Kdata

SenX

Initial release

2012

2010

1984

2016

2015

Current release

InterBase 2020, December 2019

License

Commercial or Open Source

commercial

Open Source

AGPL-V3

Open Source

Apache License 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

Java

Server operating systems

hosted

Android
iOS
Linux
OS X
Windows

All OS with a Java 7 VM

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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.

export as XML data possible

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

View functions (Map-Reduce) in JavaScript

yes

Interbase procedure and trigger language

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Interbase Change Views

Source-replica replication

selectable replication factor

based on HBase

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

Immediate Consistency

based on HBase

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

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Multiversion concurreny control

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

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 rights for users and roles

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.