DBMS > OrigoDB vs. RDF4J vs. SQLite vs. Tibero

System Properties Comparison OrigoDB vs. RDF4J vs. SQLite vs. Tibero

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.

Widely used embeddable, in-process RDBMS

A secure RDBMS, designed for easy portability from Oracle

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	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

origodb.com

rdf4j.org

www.sqlite.org

us.tmaxsoft.com/products/tibero

Technical documentation

origodb.com/docs

rdf4j.org/documentation

www.sqlite.org/docs.html

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Robert Friberg et al

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

Dwayne Richard Hipp

TmaxSoft

Initial release

2009

under the name LiveDB

2004

2000

2003

Current release

3.46.0 (23 May 2024), May 2024

6, April 2015

License

Commercial or Open Source

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Public Domain

commercial

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 Assembler

Server operating systems

Linux
Windows

Linux
OS X
Unix
Windows

server-less

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

RDF Schemas

yes

dynamic column types

yes

Typing

predefined data types such as float or date

User defined using .NET types and collections

yes

not rigid because of 'dynamic typing' concept.

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

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

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

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

.Net

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

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

yes

Persistent Stored Procedure (PSM)

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

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication
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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

planned for next version

User concepts

Access control

Role based authorization

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.