DBMS > Amazon Redshift vs. EXASOL vs. IRONdb vs. RavenDB

System Properties Comparison Amazon Redshift vs. EXASOL vs. IRONdb vs. RavenDB

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Relational DBMS

Time Series DBMS

Document store

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

aws.amazon.com/redshift

www.exasol.com

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

ravendb.net

Technical documentation

docs.aws.amazon.com/redshift

www.exasol.com/resources

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

ravendb.net/docs

Developer

Amazon (based on PostgreSQL)

Exasol

Circonus LLC.

Hibernating Rhinos

Initial release

2012

2000

2017

2010

Current release

V0.10.20, January 2018

5.4, July 2022

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

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

C and C++

Server operating systems

hosted

Linux

Linux
macOS
Raspberry Pi
Windows

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

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

SQL-like query language (RQL)

APIs and other access methods

JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Java
Lua
Python
R

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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes, in Lua

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

configurable replication factor, datacenter aware

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

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, groups and roles according to SQL-standard

Authorization levels configured per client 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.