DBMS > Amazon Redshift vs. IRONdb vs. OrigoDB vs. RDF4J vs. searchxml

System Properties Comparison Amazon Redshift vs. IRONdb vs. OrigoDB vs. RDF4J vs. searchxml

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

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

A fully ACID in-memory object graph database

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Relational DBMS

Time Series DBMS

Document store
Object oriented DBMS

RDF store

Native XML DBMS
Search engine

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

aws.amazon.com/redshift

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

origodb.com

rdf4j.org

www.searchxml.net/category/products

Technical documentation

docs.aws.amazon.com/redshift

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

origodb.com/docs

rdf4j.org/documentation

www.searchxml.net/support/handouts

Developer

Amazon (based on PostgreSQL)

Circonus LLC.

Robert Friberg et al

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

informationpartners gmbh

Initial release

2012

2017

2009

under the name LiveDB

2004

2015

Current release

V0.10.20, January 2018

1.0

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.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

C and C++

Java

C++

Server operating systems

hosted

Linux

Linux
Windows

Linux
OS X
Unix
Windows

Windows

Data scheme

yes

schema-free

yes

RDF Schemas

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

User defined using .NET types and collections

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.

can be achieved using .NET

yes

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

HTTP API

.NET Client API
HTTP API
LINQ

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net

Java
PHP
Python

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

user defined functions

in Python

yes, in Lua

yes

on the application server

Triggers

yes

Domain Events

yes

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

configurable replication factor, datacenter aware

Source-replica replication

none

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

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

depending on model

Transaction concepts

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

ACID

Isolation support depends on the API used

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

in-memory storage is supported as well

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

Role based authorization

Domain, group and role-based access control at the document level and for application services

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.