DBMS > Amazon Redshift vs. Apache Drill vs. CouchDB vs. IRONdb

System Properties Comparison Amazon Redshift vs. Apache Drill vs. CouchDB vs. IRONdb

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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

Primary database model

Relational DBMS

Document store
Relational DBMS

Document store

Time Series DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	10.26
Rank	#45	Overall
	#7	Document stores

Website

aws.amazon.com/redshift

drill.apache.org

couchdb.apache.org

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

Technical documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

docs.couchdb.org/en/stable

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

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Circonus LLC.

Initial release

2012

2005

2017

Current release

1.20.3, January 2023

3.3.3, December 2023

V0.10.20, January 2018

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache version 2

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

Server operating systems

hosted

Linux
OS X
Windows

Android
BSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

via views

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL SELECT statement is SQL:2003 compliant

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

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C++

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

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

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

View functions in JavaScript

yes, in Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Automatic, metric affinity per node

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

configurable replication factor, datacenter aware

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency

Immediate consistency per node, eventual consistency across nodes

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 single document possible

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

In-memory capabilities

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

yes

Depending on the underlying data source

User concepts

Access control

fine grained access rights according to SQL-standard

Depending on the underlying data source

Access rights for users can be defined per database

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.