DBMS > IRONdb vs. Microsoft Azure Cosmos DB vs. RavenDB vs. RDF4J

System Properties Comparison IRONdb vs. Microsoft Azure Cosmos DB vs. RavenDB vs. RDF4J

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

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

Globally distributed, horizontally scalable, multi-model database service

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.

Primary database model

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store

RDF store

Secondary database models

Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Website

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

azure.microsoft.com/services/cosmos-db

ravendb.net

rdf4j.org

Technical documentation

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

learn.microsoft.com/azure/cosmos-db

ravendb.net/docs

rdf4j.org/documentation

Developer

Circonus LLC.

Microsoft

Hibernating Rhinos

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

Initial release

2017

2014

2010

2004

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

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

C and C++

Java

Server operating systems

Linux

hosted

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

RDF Schemas

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

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

SQL-like query language

SQL-like query language (RQL)

APIs and other access methods

HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table 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

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#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

Java
PHP
Python

Server-side scripts

Stored procedures

yes, in Lua

JavaScript

yes

Triggers

JavaScript

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

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes

Implicit feature of the cloud service

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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.

Foreign keys

Referential integrity

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID, Cluster-wide transaction available

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.

User concepts

Access control

Access rights can be defined down to the item level

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.