DBMS > RDF4J vs. Riak TS vs. searchxml vs. Snowflake

System Properties Comparison RDF4J vs. Riak TS vs. searchxml vs. Snowflake

Please select another system to include it in the comparison.

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.

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

DBMS for structured and unstructured content wrapped with an application server

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

Primary database model

RDF store

Time Series DBMS

Native XML DBMS
Search engine

Relational DBMS

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

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

rdf4j.org

www.searchxml.net/category/products

www.snowflake.com

Technical documentation

rdf4j.org/documentation

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

www.searchxml.net/support/handouts

docs.snowflake.net/manuals/index.html

Developer

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

Open Source, formerly Basho Technologies

informationpartners gmbh

Snowflake Computing Inc.

Initial release

2004

2015

2014

Current release

3.0.0, September 2022

1.0

License

Commercial or Open Source

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

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

C++

Server operating systems

Linux
OS X
Unix
Windows

Linux
OS X

Windows

hosted

Data scheme

yes

RDF Schemas

schema-free

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

restricted

yes

SQL

Support of SQL

yes, limited

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

RESTful HTTP API
WebDAV
XQuery
XSLT

CLI Client
JDBC
ODBC

Supported programming languages

Java
PHP
Python

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

C++

most other programming languages supported via APIs

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Erlang

yes

on the application server

user defined functions

Triggers

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

yes

sychronisation to multiple collections

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between datasets 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

multiple readers, single writer

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.

User concepts

Access control

Domain, group and role-based access control at the document level and for application services

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.