John, Generally speaking I don't recommend that you break all of those properties down into individual nodes. Taking that approach is pretty much obviating many of the benefits of a properties based graph and what you end up with is essentially RDF with all of the associated performance problems.
The links below are some of my favorite posts on good data modeling practices although it certainly isn't 100% comprehensive. https://neo4j.com/blog/data-modeling-pitfalls/ https://neo4j.com/blog/dark-side-neo4j-worst-practices/ Sent from my iPhone > On May 1, 2017, at 04:37, John Begley <[email protected]> wrote: > > Hi, was there an update to this. The core problem I'm seeing on a graph I'm > working on is very similar. Basically I am creating a graph of people. In > order to match people I am creating separate nodes around key matching > criteria (like date of birth, first name, family name and gender). With > cleanish data going in then half the person nodes will have a relationship to > the male gender node and half to the female gender node. I'm finding that > when I ramp up the performance tests (with a unique constraint on gender) > then the performance degrades hugely but if I remove the constraint then I > get multiple gender nodes which doesn't help with matching people! > > Is there a common pattern/approach for solving this? > > Thanks, > John > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
