DBMS > OrigoDB vs. RavenDB vs. RDF4J vs. Sadas Engine

System Properties Comparison OrigoDB vs. RavenDB vs. RDF4J vs. Sadas Engine

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Document store
Object oriented DBMS

Document store

RDF store

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series 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	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

Technical documentation

origodb.com/docs

ravendb.net/docs

rdf4j.org/documentation

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Robert Friberg et al

Hibernating Rhinos

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

SADAS s.r.l.

Initial release

2009

under the name LiveDB

2010

2004

2006

Current release

5.4, July 2022

8.0

License

Commercial or Open Source

Open Source

AGPL version 3, commercial license available

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

free trial version available

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++

Server operating systems

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Unix
Windows

AIX
Linux
Windows

Data scheme

yes

schema-free

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

SQL-like query language (RQL)

yes

APIs and other access methods

.NET Client API
HTTP API
LINQ

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

JDBC
ODBC
Proprietary protocol

Supported programming languages

.Net

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

Java
PHP
Python

.Net
C
C#
C++
Groovy
Java
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

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

none

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

depending on model

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

ACID

Isolation support depends on the API used

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

managed by 'Learn by Usage'

User concepts

Access control

Role based authorization

Authorization levels configured per client per database

Access rights for users, groups and roles 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.

More resources

Recent citations in the news

RavenDB Launches Version 6.0 Lightning Fast Queries, Data Integrations, Corax Indexing Engine, and Sharding
2 October 2023, PR Newswire

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and ...
13 June 2023, PR Newswire

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

Oren Eini on RavenDB, Including Consistency Guarantees and C# as the Implementation Language
23 May 2022, InfoQ.com

RavenDB Adds Graph Queries
15 May 2019, Datanami

provided by Google News

GraphDB Goes Open Source
27 January 2020, iProgrammer

provided by Google News

Share this page