KatanaGraph vs Neptune
KatanaGraph is a other database; Neptune is a multiple database. KatanaGraph (2020-11, BSD-3-Clause, C++) ranks #74 this month; Neptune (2017-11, Proprietary, C++) ranks #4. They differ on 31 of 46 surveyed features.
| Attribute | KatanaGraph | Neptune |
|---|---|---|
| At a glance | ||
| Rank | #74 | #4 |
| Score | 43.1 | 65.5 |
| GitHub stars | 104 | — |
| Popularity | 55.8 | 81.2 |
| Activity | 30.1 | 95.5 |
| Community | 30.6 | 53.7 |
| Research | 49.6 | 58.4 |
| Fundamentals | ||
| Description | A graph computation library focused on parallel analytics and machine learning on large graphs. Features multithreaded execution with load balancing across multi-socket systems. | 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 | Katana Graph | Amazon Web Services |
| Model | Other | Multiple |
| Kind | embedded | database |
| Category | Emerging | Enterprise |
| First released | 2020-11 | 2017-11 |
| Status | inactive — Katana Graph shut down in 2023. GitHub repositories archived. | active |
| License | BSD-3-Clause | Proprietary |
| Written in | C++ | C++ |
| Query languages | openCypher | Gremlin, SPARQL, openCypher |
| gdotv support | no | yes |
Feature scores 31 of 46 rows differ
| Feature | KatanaGraph | Neptune |
|---|---|---|
| Community & Business | ||
| Active development | · | ✓ |
| Commercial support | ✓ | ✓ |
| Live community | 0.5 | ✓ |
| 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
- KatanaGraph · website · github · full profile
- Neptune · website · full profile