Eclipse RDF4J vs FalkorDB

Eclipse RDF4J is a rdf database; FalkorDB is a property graph database. Eclipse RDF4J (2002, BSD-3-Clause, Java) ranks #27 this month; FalkorDB (2018-07, SSPL-1.0, C) ranks #5.

Attribute Eclipse RDF4J #27 ▼4 Strong FalkorDB #5 ▲1 Leader
At a glance
Rank #27#5
Score 54.569.8
GitHub stars 42210.5k
Popularity 57.468.1
Activity 68.478.6
Community 36.769.8
Research 50.555.3
Fundamentals
Description A Java-based RDF framework and triple store supporting both in-memory and persistent storage. Provides SPARQL query endpoints over HTTP and a pluggable storage architecture (SAIL API) used by other triple store implementations including Ontotext GraphDB.A property graph database that runs as a Redis module, formerly RedisGraph. Uses GraphBLAS sparse matrix operations for query execution, enabling parallel graph traversal.
Vendor Eclipse FoundationFalkorDB
Model RDFProperty Graph
Kind databasedatabase
Category EstablishedEstablished
First released 20022018-07
Status activeactive
License BSD-3-ClauseSSPL-1.0
Written in JavaC
Query languages SPARQLopenCypher
gdotv support yesyes

Feature scores — not surveyed for Eclipse RDF4J

Feature Eclipse RDF4JFalkorDB
Community & Business
Active development —✓
Commercial support —✓
Live community —✓
Open Source —✓
Pricing —✓
Trendiness —0.5
Deployment
Containerization —✓
Work as dedicated instance —✓
Work as embedded —·
Testing in-memory version —✓
Platform
Operating on Linux —✓
Operating on Windows —0.75
SaaS offering —·
Operations
Automatic updates —·
Client side caching —0.5
Data versioning support —·
Live backups —0.5
Distribution
Cluster Re-balancing —·
Data Distribution —·
High-Availability —0.5
Query Distribution —·
Replication support —✓
Developer Experience
Data types defined —✓
Logging/Auditing —0.5
Object-Graph Mapper —✓
Reactive programming —0.5
Documentation up-to-date —✓
Binary protocol —✓
CLI —✓
GUI —·
Data Model
Multi-database —·
Graph-native data —✓
REST API —✓
Query Language —✓
Transactions
Granular locking —·
Multiple isolation levels —·
Read committed transaction —·
Transaction support —✓
Schema & Security
Constraints —✓
Schema support —·
Secondary indexes —✓
Server side procedures —✓
Triggers —0.5
Authentication —0.5
Authorization —0.5
Data encryption —0.5