Basic Information
| Field | Details |
|---|---|
| English name | Amazon Neptune |
| Full name | Amazon Neptune |
| Chinese description | 托管图数据库 |
| Japanese description | マネージドグラフデータベース |
| Exam frequency | ⭐⭐ |
| Often confused with | RDS / DocumentDB |
In one sentence
When relationship paths matter more than individual records, Neptune is more natural than many layers of joins.
Core purpose
- It supports graph models such as property graphs and RDF and optimizes multi-hop traversal and pattern matching.
- Use cases include social networks, fraud detection, recommendations, knowledge graphs, and network topology.
- It provides managed backups, failover, and automatically growing storage.
Exam focus
- Graph, fraud detection, recommendation, or knowledge graph usually points to Neptune.
- Ordinary foreign-key relationships do not automatically require a graph database.
- The advantage is strongest when relationship traversal is the core problem.
Common misconceptions
- Neptune is not a universal answer to every complex database problem.
- Exact capacity and quotas should be checked for the current Region and service version.
Key takeaway
When complex relationship paths are the main data, choose Neptune.
Related services
DocumentDB, DynamoDB, RDS, S3, Analytics.