DBMS > RDF4J vs. Realm vs. Riak KV vs. Snowflake vs. VelocityDB

System Properties Comparison RDF4J vs. Realm vs. Riak KV vs. Snowflake vs. VelocityDB

Editorial information provided by DB-Engines

Name

Description

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

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

Distributed, fault tolerant key-value store

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

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

RDF store

Document store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Graph DBMS
Object oriented DBMS

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

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Website

Technical documentation

rdf4j.org/documentation

realm.io/docs

www.tiot.jp/riak-docs/riak/kv/latest

docs.snowflake.net/manuals/index.html

velocitydb.com/UserGuide

Developer

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

Realm, acquired by MongoDB in May 2019

OpenSource, formerly Basho Technologies

Snowflake Computing Inc.

VelocityDB Inc

Initial release

2004

2014

2009

2014

2011

Current release

3.2.0, December 2022

7.x

License

Commercial or Open Source

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

Linux
OS X
Unix
Windows

Android
Backend: server-less
iOS
Windows

Linux
OS X

hosted

Any that supports .NET

Data scheme

yes

RDF Schemas

yes

schema-free

yes

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

yes

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

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

.Net

Supported programming languages

Java
PHP
Python

.Net
Java

with Android only
Objective-C
React Native
Swift

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

JavaScript (Node.js)
Python

.Net

Server-side scripts

Stored procedures

yes

runs within the applications so server-side scripts are unnecessary

Erlang

user defined functions

Triggers

yes

Change Listeners

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

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

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

In-Memory realm

yes

User concepts

Access control

yes

yes, using Riak Security

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

Based on Windows 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.