DBMS > IRONdb vs. PouchDB vs. RDF4J vs. SAP HANA vs. SQLite

System Properties Comparison IRONdb vs. PouchDB vs. RDF4J vs. SAP HANA vs. SQLite

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

JavaScript DBMS with an API inspired by CouchDB

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

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

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

pouchdb.com

rdf4j.org

www.sap.com/products/hana.html

www.sqlite.org

Technical documentation

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

pouchdb.com/guides

rdf4j.org/documentation

help.sap.com/hana

www.sqlite.org/docs.html

Developer

Circonus LLC.

Apache Software Foundation

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

SAP

Dwayne Richard Hipp

Initial release

2017

2012

2004

2010

2000

Current release

V0.10.20, January 2018

7.1.1, June 2019

2.0 SPS07 (April 4, 2023), April 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

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++

JavaScript

Java

Server operating systems

Linux

server-less, requires a JavaScript environment (browser, Node.js)

Linux
OS X
Unix
Windows

Appliance or cloud-service

server-less

Data scheme

schema-free

yes

RDF Schemas

yes

dynamic column types

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

not rigid because of 'dynamic typing' concept.

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

via views

yes

SQL

Support of SQL

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

yes

SQL-92 is not fully supported

APIs and other access methods

HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

JavaScript

Java
PHP
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes, in Lua

View functions in JavaScript

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

Sharding

with a proxy-based framework, named couchdb-lounge

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

yes

none

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

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.