Neo4j: Modeling Hyper Edges in a Property Graph
Neo4j: Modeling Hyper Edges in a Property Graph
Join the DZone community and get the full member experience.
Join For FreeVerify, standardize, and correct the Big 4 + more– name, email, phone and global addresses – try our Data Quality APIs now at Melissa Developer Portal!
At the Graph Database meet up in Antwerp, we discussed how you would model a hyper edge in a property graph like Neo4j, and I realized that I’d done this in my football graph without realizing.
A hyper edge is defined as follows:
A hyperedge is a connection between two or more vertices, or nodes, of a hypergraph. A hypergraph is a graph in which generalized edges (called hyperedges) may connect more than two nodes with discrete properties.
In Neo4j, an edge (or relationship) can only be between itself or another node; there’s no way of creating a relationship between more than 2 nodes.
I had problems when trying to model the relationship between a player and a football match because I wanted to say that a player participated in a match and represented a specific team in that match.
I started out with the following model:
Unfortunately, creating a direct relationship from the player to the match means that there’s no way to work out which team they played for.
This information is useful because sometimes players transfer teams in the middle of a season and we want to analyze how they performed for each team.
In a property graph, we need to introduce an extra node which links the match, player and team together:
Although we are forced to adopt this design it actually helps us realize an extra entity in our domain which wasn’t visible before – a player’s performance in a match.
If we want to capture information about a players’ performance in a match we can store it on this node.
We can also easily aggregate players stats by following the played relationship without needing to worry about the matches they played in.
The Neo4j manual has a few more examples of domain models containing hyper edges which are worth having a look at if you want to learn more.
Developers! Quickly and easily gain access to the tools and information you need! Explore, test and combine our data quality APIs at Melissa Developer Portal – home to tools that save time and boost revenue. Our APIs verify, standardize, and correct the Big 4 + more – name, email, phone and global addresses – to ensure accurate delivery, prevent blacklisting and identify risks in real-time.
Like This Article? Read More From DZone
Published at DZone with permission of Mark Needham , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}