whichdb

Eclipse RDF4J

active

by Eclipse Foundation · since 2016 · also known as RDF4J, Sesame

Eclipse Foundation's Java RDF framework with native, LMDB and in-memory SPARQL stores.

rdf / triple storedatabase engineopen source (permissive)mature
Website Docs Source★ 422 Compare Find similar

Overview

Eclipse RDF4J, the successor to Sesame, is a Java framework for working with RDF: parsers and writers for every major format, a SPARQL 1.1 query and update engine, SHACL validation, federation (FedX), and pluggable stores including an in-memory store, the disk-based Native Store and an LMDB-backed store. RDF4J Server and Workbench expose repositories over the standard SPARQL protocol, and its SAIL API is the foundation of commercial triplestores such as GraphDB. It is the practical choice for Java teams that want an embeddable, BSD-licensed RDF store or a common API in front of several triplestores; for very large datasets, pair it with a dedicated backend.

Knowledge graphEmbedded / in-processMetadata & config

Strengths & trade-offs

Strengths

  • +Complete Java RDF toolkit: parsers, SPARQL engine, SHACL and federation
  • +Embeddable stores (memory, Native, LMDB) with transactional semantics
  • +SAIL API lets one codebase target GraphDB, Neptune or other SPARQL backends
  • +Permissive BSD license under Eclipse Foundation governance

Trade-offs

  • −Built-in stores are not designed for billion-triple datasets
  • −No clustering or replication in the open-source server
  • −Java-only API

Great for

  • +Embedding RDF storage in Java applications
  • +SHACL validation pipelines
  • +A common RDF API across multiple triplestores
  • +Federated SPARQL queries

Think twice for

  • −Very large public SPARQL endpoints
  • −Non-JVM stacks
  • −Property-graph workloads

Capabilities

Native or official first-party support · 5 of 25 tracked

✓Transactions
✓Full-text search
✓Geospatial
✓In-memory
✓Durable persistence
–Joins
–Secondary indexes
–Vector search
–JSON
–Change data capture
–Triggers
–Stored procedures
–Materialized views
–TTL / expiry
–Pub/Sub
–Columnar storage
–Compression
–Encryption at rest
–Role-based access
–Time travel
–Branching
–Online schema changes
–Streaming ingest
–Offline sync
–Runs in WebAssembly

Scale & consistency

Comfortable data size
Small · ≤ 100 GB
Horizontal scaling
None
Multi-region
No
Transactions
Full ACID
Consistency
Strong
Schema
Schemaless
Architecture
Embedded, Single node, Client server
Query languages
SPARQL

Native and LMDB stores handle up to hundreds of millions of triples per repository.

Deployment

Self-hosted Vendor-managed cloud Serverless Embedded Edge Kubernetes operator

Ecosystem

apis & protocolsRDF4J Java API (SAIL), SPARQL protocol, RDF4J REST API
client languagesJava

Alternatives to Eclipse RDF4J

Compare all→
Apache Jena TDBRDF / Triple Store18.9

Apache Jena's native RDF store, embeddable in Java or served over SPARQL with Fuseki.

eclipse-rdf4j vs apache-jena-tdb →
Graphwise GraphDB (Ontotext)RDF / Triple Store15.6

Standards-compliant RDF triplestore with reasoning, connectors and MCP support for GraphRAG.

eclipse-rdf4j vs ontotext-graphdb →
OxigraphRDF / Triple Store15.1

Small, fast SPARQL database in Rust that embeds in Rust, Python and JavaScript or runs as a server.

eclipse-rdf4j vs oxigraph →
OpenLink VirtuosoRDF / Triple Store19.5

Hybrid SQL/RDF engine that runs many of the largest public SPARQL endpoints.

eclipse-rdf4j vs virtuoso →
QLeverRDF / Triple Store17.9

Fast open-source SPARQL engine that serves all of Wikidata or OpenStreetMap from one machine.

eclipse-rdf4j vs qlever →
RDFoxRDF / Triple Store3.4

In-memory RDF store with incremental Datalog reasoning, now owned by Samsung.

eclipse-rdf4j vs rdfox →

Eclipse RDF4J FAQ

What is Eclipse RDF4J?

Eclipse RDF4J is a RDF / triple store database by Eclipse Foundation, first released in 2016. Eclipse RDF4J, the successor to Sesame, is a Java framework for working with RDF: parsers and writers for every major format, a SPARQL 1.1 query and update engine, SHACL validation, federation (FedX), and pluggable stores including an in-memory store, the disk-based Native Store and an LMDB-backed store. RDF4J Server and Workbench expose repositories over the standard SPARQL protocol, and its SAIL API is the foundation of commercial triplestores such as GraphDB. It is the practical choice for Java teams that want an embeddable, BSD-licensed RDF store or a common API in front of several triplestores; for very large datasets, pair it with a dedicated backend.

Is Eclipse RDF4J open source?

Yes. Eclipse RDF4J is open source. License: BSD 3-Clause License.

Does Eclipse RDF4J support ACID transactions?

Yes. Eclipse RDF4J supports full ACID transactions, with strong consistency.

Does Eclipse RDF4J scale horizontally?

Eclipse RDF4J does not scale horizontally; it runs on a single node, so you scale it up rather than out. It is comfortable at small scale (≤ 100 GB).

How can I run Eclipse RDF4J?

You can self-host it and embed it in your application.

What is Eclipse RDF4J best for?

Eclipse RDF4J is a strong fit for embedding RDF storage in Java applications, SHACL validation pipelines and A common RDF API across multiple triplestores. Think twice for very large public SPARQL endpoints.

What are the best alternatives to Eclipse RDF4J?

Common alternatives to Eclipse RDF4J include Apache Jena TDB, Graphwise GraphDB (Ontotext), Oxigraph, OpenLink Virtuoso and QLever. The right choice depends on your workload, scale and hosting; WhichDB's smart match ranks them against your requirements.

How popular is Eclipse RDF4J?

Eclipse RDF4J ranks #296 of 844 databases on the WhichDB Score (10.6/100), and #8 among RDF / triple store databases. The score combines public adoption signals such as package downloads, GitHub activity, job posts and developer discussion.