HyperGraphDB vs Neptune

HyperGraphDB is a other database; Neptune is a multiple database. HyperGraphDB (2007, Apache-2.0, Java) ranks #58 this month; Neptune (2017-11, Proprietary, C++) ranks #14. They differ on 33 of 46 surveyed features.

Attribute HyperGraphDB #58 ▼2 Growing Neptune #14 ▲2 Strong
At a glance
Rank #58#14
Score 45.461.1
GitHub stars 250—
Popularity 41.561.0
Activity 32.460.9
Community 60.561.8
Research 53.760.4
Fundamentals
Description An open-source embedded database for storing hypergraphs, where edges can connect any number of vertices. Uses BerkeleyDB for low-level storage and supports ACID transactions with MVCC conflict detection.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 —Amazon Web Services
Model OtherMultiple
Kind embeddeddatabase
Category EmergingEnterprise
First released 20072017-11
Status inactive — Sporadic maintenance only since 2024active
License Apache-2.0Proprietary
Written in JavaC++
Query languages Java APIGremlin, SPARQL, openCypher
gdotv support noyes

Feature scores 33 of 46 rows differ

Feature HyperGraphDBNeptune
Community & Business
Active development 0.5✓
Commercial support ·✓
Live community 0.5✓
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.5·
SaaS offering ·✓
Operations
Automatic updates ·✓
Client side caching ✓✓
Data versioning support ✓·
Live backups ·✓
Distribution
Cluster Re-balancing ··
Data Distribution 0.25·
High-Availability ·✓
Query Distribution 0.250.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 0.5✓
Transactions
Granular locking ·✓
Multiple isolation levels 0.5✓
Read committed transaction 0.25✓
Transaction support ✓✓
Schema & Security
Constraints ✓✓
Schema support 0.50.5
Secondary indexes ✓✓
Server side procedures ··
Triggers 0.5·
Authentication ·✓
Authorization ·✓
Data encryption ·✓