Apache Jena Fuseki vs Neo4j
Apache Jena Fuseki is a rdf database; Neo4j is a property graph database. Apache Jena Fuseki (2010-10, Apache-2.0, Java) ranks #22 this month; Neo4j (2007, GPL-3.0, Java) ranks #1.
Choosing between them
These two use different data models. Fuseki is an Apache-2.0 RDF triple store that serves the SPARQL 1.1 query, update and Graph Store protocols. Jena adds RDFS, OWL (a rule-based subset) and general rule reasoners. Pick Fuseki when your data is published or exchanged as RDF, when you work with shared vocabularies and ontologies, or when you need standards-based reasoning.
Neo4j is a property graph database queried with Cypher and GQL. It reads and writes RDF through neosemantics, a Neo4j Labs plugin that works on self-hosted Neo4j and is not available on the Aura cloud service. Pick Neo4j when your application queries the graph directly and RDF interchange is occasional.
| Attribute | Apache Jena Fuseki | Neo4j |
|---|---|---|
| At a glance | ||
| Rank | #22 | #1 |
| Score | 55.8 | 88.8 |
| GitHub stars | 1.5k | 17.3k |
| Popularity | 65.5 | 98.6 |
| Activity | 62.4 | 86.5 |
| Community | 31.5 | 73.8 |
| Research | 63.5 | 98.7 |
| Fundamentals | ||
| Description | An open-source RDF triple store and SPARQL server built on the Apache Jena framework. Uses the TDB2 native storage engine with support for GeoSPARQL spatial queries. | A property graph database that stores data as fixed-size records in linked lists for index-free adjacency traversal. Offers community and commercial editions with an extensive graph algorithms library. |
| Vendor | Apache Software Foundation | Neo4j Inc |
| Model | RDF | Property Graph |
| Kind | database | database |
| Category | Established | Established |
| First released | 2010-10 | 2007 |
| Status | active | active |
| License | Apache-2.0 | GPL-3.0 |
| Written in | Java | Java |
| Query languages | SPARQL | Cypher, GQL |
| gdotv support | yes | yes |
Feature scores — not surveyed for Apache Jena Fuseki
| Feature | Apache Jena Fuseki | Neo4j |
|---|---|---|
| Community & Business | ||
| Active development | — | ✓ |
| Commercial support | — | ✓ |
| Live community | — | ✓ |
| Open Source | — | ✓ |
| Pricing | — | 0.5 |
| Trendiness | — | ✓ |
| Deployment | ||
| Containerization | — | ✓ |
| Work as dedicated instance | — | ✓ |
| Work as embedded | — | ✓ |
| Testing in-memory version | — | ✓ |
| Platform | ||
| Operating on Linux | — | ✓ |
| Operating on Windows | — | ✓ |
| SaaS offering | — | ✓ |
| Operations | ||
| Automatic updates | — | · |
| Client side caching | — | · |
| Data versioning support | — | · |
| Live backups | — | ✓ |
| Distribution | ||
| Cluster Re-balancing | — | · |
| Data Distribution | — | ✓ |
| High-Availability | — | ✓ |
| Query Distribution | — | ✓ |
| Replication support | — | ✓ |
| Developer Experience | ||
| Data types defined | — | ✓ |
| Logging/Auditing | — | ✓ |
| Object-Graph Mapper | — | ✓ |
| Reactive programming | — | ✓ |
| 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 | — | ✓ |
| Authentication | — | ✓ |
| Authorization | — | ✓ |
| Data encryption | — | · |
Links
- Apache Jena Fuseki · website · github · full profile
- Neo4j · website · github · full profile