DBMS > RavenDB vs. RDF4J vs. RDFox vs. Snowflake

System Properties Comparison RavenDB vs. RDF4J vs. RDFox vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

High performance knowledge graph and semantic reasoning engine

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Relational DBMS

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

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	0.29
Rank	#300	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

ravendb.net

rdf4j.org

www.oxfordsemantic.tech

www.snowflake.com

Technical documentation

ravendb.net/docs

rdf4j.org/documentation

docs.oxfordsemantic.tech

docs.snowflake.net/manuals/index.html

Developer

Hibernating Rhinos

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

Oxford Semantic Technologies

Snowflake Computing Inc.

Initial release

2010

2004

2017

2014

Current release

5.4, July 2022

6.0, Septermber 2022

License

Commercial or Open Source

Open Source

AGPL version 3, commercial license available

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

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

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Unix
Windows

Linux
macOS
Windows

hosted

Data scheme

schema-free

yes

RDF Schemas

yes

RDF schemas

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (RQL)

yes

APIs and other access methods

.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

RESTful HTTP API
SPARQL 1.1

CLI Client
JDBC
ODBC

Supported programming languages

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

Java
PHP
Python

C
Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

replication via a shared file system

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 in stand-alone mode, Eventual Consistency in replicated setups

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID, Cluster-wide transaction available

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Authorization levels configured per client per database

Roles, resources, and access types

Users with fine-grained authorization concept, user roles and pluggable authentication

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.