Brand new to graph databases in general and trying to design a system using appropriate technology. 20+ years experience in the RDBMS realm and adding yet another new tool to the toolbox.
I'm trying to design a model that identifies people and communitions between them. For example, Person:A sends Communication:Email to Person:B. I can identify that each person is a node, and it's logical to assume that each person has a property for email address. However, in this universe it's not possible to assume an email is unique to any given Person (nor is any other type of communication, ie: phone call, facebook message, SMS message, etc). Does that mean the value for email is itself a node? My gut feeling is that it is not, but my RDBMS background is yelling at me to ensure uniqueness! I also identify the actual email as another node as that is a specific instance of a Communication, links People nodes, and has properties unto itself.
So in my current model, we have lots of methods of communications, none of which can be considered unique to an individual Person, and none of which are required. Do Person nodes just have properties for each communication type and we let queries perform the necessary aggregation (how many emails from address A to adres B)? Or instead is the address of a communication enough to warrant that it is itself a node?