DBMS > Amazon Redshift vs. IBM Cloudant vs. IRONdb vs. OrigoDB

System Properties Comparison Amazon Redshift vs. IBM Cloudant vs. IRONdb vs. OrigoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb 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

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

A fully ACID in-memory object graph database

Primary database model

Relational DBMS

Document store

Time Series DBMS

Document store
Object oriented DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	2.85
Rank	#95	Overall
	#18	Document stores

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Website

aws.amazon.com/redshift

www.ibm.com/products/cloudant

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

origodb.com

Technical documentation

docs.aws.amazon.com/redshift

cloud.ibm.com/docs/Cloudant

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

origodb.com/docs

Developer

Amazon (based on PostgreSQL)

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Circonus LLC.

Robert Friberg et al

Initial release

2012

2010

2017

2009

under the name LiveDB

Current release

V0.10.20, January 2018

License

Commercial or Open Source

commercial

Open Source

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

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

User defined using .NET types and collections

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.

can be achieved using .NET

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)

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

HTTP API

.NET Client API
HTTP API
LINQ

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

.Net

Server-side scripts

Stored procedures

user defined functions

in Python

View functions (Map-Reduce) in JavaScript

yes, in Lua

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

configurable replication factor, datacenter aware

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

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

depending on model

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

Write ahead log

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

Role based authorization

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.