DBMS > RDF4J vs. RocksDB vs. SAP HANA vs. SAP SQL Anywhere vs. Splunk

System Properties Comparison RDF4J vs. RocksDB vs. SAP HANA vs. SAP SQL Anywhere vs. Splunk

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.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

In-memory, column based data store. Available as appliance or cloud service

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Analytics Platform for Big Data

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

rdf4j.org

rocksdb.org

www.sap.com/products/hana.html

www.sap.com/products/technology-platform/sql-anywhere.html

www.splunk.com

Technical documentation

rdf4j.org/documentation

github.com/facebook/rocksdb/wiki

help.sap.com/hana

help.sap.com/docs/SAP_SQL_Anywhere

docs.splunk.com/Documentation/Splunk

Developer

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

Facebook, Inc.

SAP

formerly Sybase

Splunk Inc.

Initial release

2004

2013

2010

1992

2003

Current release

9.2.1, May 2024

2.0 SPS07 (April 4, 2023), April 2023

17, July 2015

License

Commercial or Open Source

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

BSD

commercial

Limited free edition and free developer edition available

Cloud-based only

Only available as a cloud service

also available as a cloud based 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
OS X
Unix
Windows

Linux

Appliance or cloud-service

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Data scheme

yes

RDF Schemas

schema-free

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

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

APIs and other access methods

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

C++ API
Java API

JDBC
ODBC

ADO.NET
HTTP API
JDBC
ODBC

HTTP REST

Supported programming languages

Java
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

SQLScript, R

yes, in C/C++, Java, .Net or Perl

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

yes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication

Database mirroring

Multi-source replication

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

yes

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

yes

fine grained access rights according to SQL-standard

Access rights for users and roles

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.