Neptune vs TerminusDB
Both are multiple databases. Neptune (2017-11, Proprietary, C++) ranks #4 this month; TerminusDB (2019-10, Apache-2.0, Prolog) ranks #34. They differ on 21 of 46 surveyed features.
| Attribute | Neptune | TerminusDB |
|---|---|---|
| At a glance | ||
| Rank | #4 | #34 |
| Score | 65.5 | 53.8 |
| GitHub stars | — | 3.4k |
| Popularity | 81.2 | 61.6 |
| Activity | 95.5 | 68.9 |
| Community | 53.7 | 35.3 |
| Research | 58.4 | 49.6 |
| Fundamentals | ||
| Description | 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). | A graph database and document store that builds knowledge graphs from JSON documents. Uses git-like delta encoding with an append-only layered data model, enabling version control and collaboration workflows. |
| Vendor | Amazon Web Services | DFRNT |
| Model | Multiple | Multiple |
| Kind | database | database |
| Category | Enterprise | Emerging |
| First released | 2017-11 | 2019-10 |
| Status | active | active |
| License | Proprietary | Apache-2.0 |
| Written in | C++ | Prolog |
| Query languages | Gremlin, SPARQL, openCypher | WOQL, GraphQL |
| gdotv support | yes | no |
Feature scores 21 of 46 rows differ
| Feature | Neptune | TerminusDB |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | ✓ |
| Commercial support | ✓ | ✓ |
| Live community | ✓ | 0.75 |
| Open Source | · | ✓ |
| Pricing | ✓ | ✓ |
| Trendiness | ✓ | ✓ |
| 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 | ✓ | · |
| 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 | 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 | ✓ | 0.5 |
| 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
- Neptune · website · full profile
- TerminusDB · website · github · full profile