DBMS > IRONdb vs. RDF4J vs. SQLite vs. TimescaleDB

System Properties Comparison IRONdb vs. RDF4J vs. SQLite vs. TimescaleDB

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

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

Widely used embeddable, in-process RDBMS

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Secondary database models

Relational DBMS

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

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

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

rdf4j.org

www.sqlite.org

www.timescale.com

Technical documentation

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

rdf4j.org/documentation

www.sqlite.org/docs.html

docs.timescale.com

Developer

Circonus LLC.

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

Dwayne Richard Hipp

Timescale

Initial release

2017

2004

2000

2017

Current release

V0.10.20, January 2018

3.45.3 (15 April 2024), April 2024

2.13.0, November 2023

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Public Domain

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud 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

Linux
OS X
Unix
Windows

server-less

Linux
OS X
Windows

Data scheme

schema-free

yes

RDF Schemas

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

not rigid because of 'dynamic typing' concept.

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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.

yes

Secondary indexes

yes

SQL

Support of SQL

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

yes

SQL-92 is not fully supported

yes

full PostgreSQL SQL syntax

APIs and other access methods

HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

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

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes, in Lua

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

none

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

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

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

fine grained access rights according to SQL-standard

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.