DBMS > OrigoDB vs. RDF4J vs. Transbase

System Properties Comparison OrigoDB vs. RDF4J vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A fully ACID in-memory object graph database

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store
Object oriented DBMS

RDF store

Relational DBMS

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

Score	0.00
Rank	#379	Overall
	#54	Document stores
	#20	Object oriented DBMS

Score	0.83
Rank	#202	Overall
	#7	RDF stores

Score	0.00
Rank	#379	Overall
	#155	Relational DBMS

Website

origodb.com

rdf4j.org

www.transaction.de/en/products/transbase.html

Technical documentation

origodb.com/docs

rdf4j.org/documentation

www.transaction.de/en/products/transbase/features.html

Developer

Robert Friberg et al

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

Transaction Software GmbH

Initial release

2009

under the name LiveDB

2004

1987

Current release

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

free development 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

Java

C and C++

Server operating systems

Linux
Windows

Linux
OS X
Unix
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

RDF Schemas

yes

Typing

predefined data types such as float or date

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

.NET Client API
HTTP API
LINQ

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net

Java
PHP
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

Share this page