DBMS > Amazon Redshift vs. IBM Cloudant vs. IRONdb vs. Tkrzw vs. Yaacomo

System Properties Comparison Amazon Redshift vs. IBM Cloudant vs. IRONdb vs. Tkrzw vs. Yaacomo

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Yaacomo seems to be discontinued and is removed 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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

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	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

aws.amazon.com/redshift

www.ibm.com/products/cloudant

www.circonus.com/solutions/time-series-database/

dbmx.net/tkrzw

yaacomo.com

Technical documentation

docs.aws.amazon.com/redshift

cloud.ibm.com/docs/Cloudant

docs.circonus.com/irondb/category/getting-started

Developer

Amazon (based on PostgreSQL)

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Circonus LLC.

Mikio Hirabayashi

Q2WEB GmbH

Initial release

2012

2010

2017

2020

2009

Current release

V0.10.20, January 2018

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

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++

C++

Server operating systems

hosted

Linux

Linux
macOS

Android
Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

HTTP API

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

View functions (Map-Reduce) in JavaScript

yes, in Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

configurable replication factor, datacenter aware

none

Source-replica replication

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 per node, eventual consistency across nodes

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

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

using specific database classes

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

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.