Database Reference
In-Depth Information
Graph database modeling pitfalls
As with any type of database modeling, a graph database will also have some pitfalls
that we would want to try and avoid. This section will by no means attempt to give
you an exhaustive list, but should give you a feel for the types of practices that can
lead to poor modeling decisions.
Using "rich" properties
As it is actually a best practice to have a very granular model in in-graph database
systems, the opposite of this can often be an antipattern. Using properties on a node
thatareostensiblytoorich(asshowninthefollowingigure)canbemuchbetter
solved by leveraging the model, splitting off the properties into separate nodes,
and connecting them using a relationship:
Using "rich" properties
Look at the following diagram for a potential solution to this antipattern:
Granulating "rich" properties
