DBMS > etcd vs. IRONdb vs. RDF4J vs. SQLite vs. XTDB

System Properties Comparison etcd vs. IRONdb vs. RDF4J vs. SQLite vs. XTDB

Editorial information provided by DB-Engines

Name

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

Description

A distributed reliable key-value store

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 general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

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

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

etcd.io
github.com/etcd-io/etcd

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

rdf4j.org

www.sqlite.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

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

rdf4j.org/documentation

www.sqlite.org/docs.html

www.xtdb.com/docs

Developer

Circonus LLC.

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

Dwayne Richard Hipp

Juxt Ltd.

Initial release

2017

2004

2000

2019

Current release

3.4, August 2019

V0.10.20, January 2018

3.45.3 (15 April 2024), April 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Public Domain

Open Source

MIT License

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

Clojure

Server operating systems

FreeBSD
Linux
Windows

experimental

Linux

Linux
OS X
Unix
Windows

server-less

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

RDF Schemas

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

not rigid because of 'dynamic typing' concept.

yes, extensible-data-notation format

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)

yes

SQL-92 is not fully supported

limited SQL, making use of Apache Calcite

APIs and other access methods

gRPC
JSON over HTTP

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

HTTP REST
JDBC

Supported programming languages

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

.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

Clojure
Java

Server-side scripts

Stored procedures

yes, in Lua

yes

Triggers

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

none

Replication methods

Methods for redundantly storing data on multiple nodes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

configurable replication factor, datacenter aware

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

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

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

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.