DBMS > Apache Jena - TDB vs. Firebolt vs. RavenDB vs. Realm vs. RocksDB

System Properties Comparison Apache Jena - TDB vs. Firebolt vs. RavenDB vs. Realm vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

A RDF storage and query DBMS, shipped as an optional-use component of the Apache Jena framework

Highly scalable cloud data warehouse and analytics product

Forked from Clickhouse

Open Source Operational and Transactional Enterprise NoSQL Document Database

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	3.62
Rank	#83	Overall
	#3	RDF stores

Score	1.73
Rank	#140	Overall
	#63	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

jena.apache.org/documentation/tdb/index.html

Technical documentation

jena.apache.org/documentation/tdb/index.html

docs.firebolt.io

ravendb.net/docs

realm.io/docs

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

originally developed by HP Labs

Firebolt Analytics Inc.

Hibernating Rhinos

Realm, acquired by MongoDB in May 2019

Facebook, Inc.

Initial release

2000

2020

2010

2014

2013

Current release

4.9.0, July 2023

5.4, July 2022

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache License, Version 2.0

commercial

Open Source

AGPL version 3, commercial license available

Open Source

BSD

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

Java

C++

Server operating systems

All OS with a Java VM

hosted

Linux
macOS
Raspberry Pi
Windows

Android
Backend: server-less
iOS
Windows

Linux

Data scheme

yes

RDF Schemas

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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

yes

SQL-like query language (RQL)

APIs and other access methods

Fuseki

REST-style SPARQL HTTP Interface
Jena RDF API
RIO

RDF Input/Output

.Net
ODBC
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

C++ API
Java API

Supported programming languages

Java

Go
JavaScript (Node.js)
Python

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

.Net
Java

with Android only
Objective-C
React Native
Swift

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

runs within the applications so server-side scripts are unnecessary

Triggers

yes

via event handler

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

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

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

Transaction concepts

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

ACID

TDB Transactions

ACID, Cluster-wide transaction available

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

In-Memory realm

yes

User concepts

Access control

Access control via Jena Security

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.