DBMS > RDF4J vs. SpatiaLite vs. Sphinx vs. SQLite

System Properties Comparison RDF4J vs. SpatiaLite vs. Sphinx vs. SQLite

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.

Spatial extension of SQLite

Open source search engine for searching in data from different sources, e.g. relational databases

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Relational DBMS

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

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

rdf4j.org

www.gaia-gis.it/fossil/libspatialite/index

sphinxsearch.com

www.sqlite.org

Technical documentation

rdf4j.org/documentation

www.gaia-gis.it/gaia-sins/spatialite_topics.html

sphinxsearch.com/docs

www.sqlite.org/docs.html

Developer

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

Alessandro Furieri

Sphinx Technologies Inc.

Dwayne Richard Hipp

Initial release

2004

2008

2001

2000

Current release

5.0.0, August 2020

3.5.1, February 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Open Source

GPL version 2, commercial licence available

Open Source

Public Domain

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

C++

Server operating systems

Linux
OS X
Unix
Windows

server-less

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

server-less

Data scheme

yes

RDF Schemas

yes

dynamic column types

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.

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

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

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java
PHP
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

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

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

The original contents of fields are not stored in the Sphinx index.

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

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.