Eclipse RDF4J vs Neptune
Eclipse RDF4J is a rdf database; Neptune is a multiple database. Eclipse RDF4J (2002, BSD-3-Clause, Java) ranks #27 this month; Neptune (2017-11, Proprietary, C++) ranks #14.
| Attribute | Eclipse RDF4J | Neptune |
|---|---|---|
| At a glance | ||
| Rank | #27 | #14 |
| Score | 54.5 | 61.1 |
| GitHub stars | 422 | — |
| Popularity | 57.4 | 61.0 |
| Activity | 68.4 | 60.9 |
| Community | 36.7 | 61.8 |
| Research | 50.5 | 60.4 |
| 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 fully managed graph database service from AWS supporting both property graph and RDF models. Available as Neptune Database (for transactional workloads) and Neptune Analytics (for analytical queries). |
| Vendor | Eclipse Foundation | Amazon Web Services |
| Model | RDF | Multiple |
| Kind | database | database |
| Category | Established | Enterprise |
| First released | 2002 | 2017-11 |
| Status | active | active |
| License | BSD-3-Clause | Proprietary |
| Written in | Java | C++ |
| Query languages | SPARQL | Gremlin, SPARQL, openCypher |
| gdotv support | yes | yes |
Feature scores — not surveyed for Eclipse RDF4J
| Feature | Eclipse RDF4J | Neptune |
|---|---|---|
| Community & Business | ||
| Active development | — | ✓ |
| Commercial support | — | ✓ |
| Live community | — | ✓ |
| Open Source | — | · |
| Pricing | — | ✓ |
| 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 | — | 0.5 |
| Replication support | — | ✓ |
| Developer Experience | ||
| Data types defined | — | 0.5 |
| 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 | — | 0.5 |
| Secondary indexes | — | ✓ |
| Server side procedures | — | · |
| Triggers | — | · |
| Authentication | — | ✓ |
| Authorization | — | ✓ |
| Data encryption | — | ✓ |
Links
- Eclipse RDF4J · website · github · full profile
- Neptune · website · full profile