DBMS > IRONdb vs. Microsoft Azure Table Storage vs. RavenDB vs. RDF4J vs. SAP HANA

System Properties Comparison IRONdb vs. Microsoft Azure Table Storage vs. RavenDB vs. RDF4J vs. SAP HANA

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A Wide Column Store for rapid development using massive semi-structured datasets

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

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

azure.microsoft.com/en-us/services/storage/tables

ravendb.net

rdf4j.org

www.sap.com/products/hana.html

Technical documentation

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

ravendb.net/docs

rdf4j.org/documentation

help.sap.com/hana

Developer

Circonus LLC.

Microsoft

Hibernating Rhinos

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

SAP

Initial release

2017

2012

2010

2004

2010

Current release

V0.10.20, January 2018

5.4, July 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

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

Linux

hosted

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Unix
Windows

Appliance or cloud-service

Data scheme

schema-free

yes

RDF Schemas

yes

Typing

predefined data types such as float or date

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

yes

SQL

Support of SQL

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

SQL-like query language (RQL)

yes

APIs and other access methods

HTTP API

RESTful 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

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

JDBC
ODBC

Supported programming languages

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

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

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

Java
PHP
Python

Server-side scripts

Stored procedures

yes, in Lua

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

Sharding

Implicit feature of the cloud service

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

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.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

optimistic locking

ACID, Cluster-wide transaction available

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Access rights based on private key authentication or shared access signatures

Authorization levels configured per client per database

yes

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.