Data Modeling with Graphs - Graph Databases - page 40

That is, starting from the user who reported the problem, we MATCH against all assets in
the graph along an undirected path of length 1 to 5. We store asset nodes with a sta
tus property whose value is 'down' in our results. The exclamation mark in asset.sta
tus! ensures that assets that lack a status property are not included in the results.
RETURN DISTINCT asset ensures that unique assets are returned in the results, no matter
how many times they are matched.
Given that such a query is readily supported by our graph, we gain confidence that the
design is fit for purpose.
Cross-Domain Models
Business insight often depends on us understanding the hidden network effects at play
in a complex value chain. To generate this understanding, we need to join domains
together without distorting or sacrificing the details particular to each domain. Property
graphs provide a solution here. Using a property graph, we can model a value chain as
a graph of graphs in which specific relationships connect and distinguish constituent
subdomains.
In Figure 3-6 we see a graph representation of the value chain surrounding the pro‐
duction and consumption of Shakespearean literature. Here we have high-quality in‐
formation about Shakespeare and some of his plays, together with details of one of the
companies that has recently performed the plays, plus a theatrical venue, and some
geospatial data. We've even added a review. In all, the graph describes and connects three
different domains. In the diagram we've distinguished these three domains with dif‐
ferently formatted relationships: dotted for the literary domain, solid for the theatrical
domain, and dashed for the geospatial domain.