DBMS > RDF4J vs. SiteWhere vs. Splunk vs. SQLite vs. SwayDB

System Properties Comparison RDF4J vs. SiteWhere vs. Splunk vs. SQLite vs. SwayDB

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.

M2M integration platform for persisting/querying time series data

Analytics Platform for Big Data

Widely used embeddable, in-process RDBMS

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

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

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

rdf4j.org

github.com/sitewhere/sitewhere

www.splunk.com

www.sqlite.org

swaydb.simer.au

Technical documentation

rdf4j.org/documentation

sitewhere1.sitewhere.io/index.html

docs.splunk.com/Documentation/Splunk

www.sqlite.org/docs.html

Developer

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

SiteWhere

Splunk Inc.

Dwayne Richard Hipp

Simer Plaha

Initial release

2004

2010

2003

2000

2018

Current release

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Common Public Attribution License Version 1.0

commercial

Limited free edition and free developer edition available

Open Source

Public Domain

Open Source

GNU Affero GPL V3.0

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

Scala

Server operating systems

Linux
OS X
Unix
Windows

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

server-less

Data scheme

yes

RDF Schemas

predefined scheme

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

Splunk Search Processing Language for search commands

yes

SQL-92 is not fully supported

APIs and other access methods

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java
PHP
Python

C#
Java
JavaScript
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Java
Kotlin
Scala

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on HBase

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

based on HBase

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

Immediate Consistency

Eventual Consistency

Immediate 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

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

ACID

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Users with fine-grained authorization concept

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.