DBMS > Amazon Redshift vs. Axibase vs. BaseX vs. IRONdb vs. RDF4J

System Properties Comparison Amazon Redshift vs. Axibase vs. BaseX vs. IRONdb vs. RDF4J

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

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

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

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

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.29
Rank	#292	Overall
	#25	Time Series DBMS

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Website

aws.amazon.com/redshift

axibase.com/docs/atsd/finance

basex.org

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

rdf4j.org

Technical documentation

docs.aws.amazon.com/redshift

docs.basex.org

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

rdf4j.org/documentation

Developer

Amazon (based on PostgreSQL)

Axibase Corporation

BaseX GmbH

Circonus LLC.

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

Initial release

2012

2013

2007

2017

2004

Current release

15585

10.7, August 2023

V0.10.20, January 2018

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

BSD license

commercial

Open Source

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

Java

C and C++

Java

Server operating systems

hosted

Linux

Linux
OS X
Windows

Linux

Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

yes

RDF Schemas

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

XQuery supports types

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

SQL-like query language

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

APIs and other access methods

JDBC
ODBC

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

All languages supporting JDBC/ODBC

Go
Java
PHP
Python
R
Ruby

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

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

Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

yes, in Lua

yes

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Automatic, metric affinity per node

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

configurable replication factor, datacenter aware

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate 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

multiple readers, single writer

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

Users with fine-grained authorization concept on 4 levels

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.