Service - Graph Handler: Difference between revisions
(Created page with "= Overview = Service that manages a graph database, intended to be deployed any number of times, each instance managing one graph within a project. Most relationships will be...") |
No edit summary |
||
| Line 7: | Line 7: | ||
= Repository = | = Repository = | ||
https://bitbucket.org/stb_working/ | https://bitbucket.org/stb_working/graph-handler/src/master/ | ||
= Neptune graph = | = Neptune graph = | ||
Revision as of 02:42, 1 March 2021
Overview
Service that manages a graph database, intended to be deployed any number of times, each instance managing one graph within a project. Most relationships will be stored here, other services can duplicate relationship data if they choose or can use this graph as their source.
As the project grows relationship data can be extended to allow for analysis of relationships, weighting same type connections etc..
Repository
https://bitbucket.org/stb_working/graph-handler/src/master/
Neptune graph
deploys one Neptune graph, using the property graph structure.
DynamoDB tables
Standard Config Table Per Service
Configuration tags
...
Query language
Focus on using Apache TinkerPop Gremlin for queries as it is the standard used by AWS Neptune for Property Graphs.
Querying data in graph database
Planning all Put/Update/Delete queries to pass through an API/Lambda, however Read/Get queries are able to query the graph directly.