DBMS > Amazon Redshift vs. EJDB vs. EXASOL vs. IRONdb vs. SiteWhere

System Properties Comparison Amazon Redshift vs. EJDB vs. EXASOL vs. IRONdb vs. SiteWhere

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

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

M2M integration platform for persisting/querying time series data

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	0.27
Rank	#297	Overall
	#44	Document stores

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

aws.amazon.com/redshift

github.com/Softmotions/ejdb

www.exasol.com

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

github.com/sitewhere/sitewhere

Technical documentation

docs.aws.amazon.com/redshift

github.com/Softmotions/ejdb/blob/master/README.md

www.exasol.com/resources

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

sitewhere1.sitewhere.io/index.html

Developer

Amazon (based on PostgreSQL)

Softmotions

Exasol

Circonus LLC.

SiteWhere

Initial release

2012

2000

2017

2010

Current release

V0.10.20, January 2018

License

Commercial or Open Source

commercial

Open Source

GPLv2

commercial

Open Source

Common Public Attribution License Version 1.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

C and C++

Java

Server operating systems

hosted

server-less

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

schema-free

predefined scheme

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

yes

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

APIs and other access methods

JDBC
ODBC

in-process shared library

.Net
JDBC
ODBC
WebSocket

HTTP API

HTTP REST

Supported programming languages

All languages supporting JDBC/ODBC

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes, in Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Automatic, metric affinity per node

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

configurable replication factor, datacenter aware

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write 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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users, groups and roles according to SQL-standard

Users with fine-grained authorization concept

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.