Is there any recommendation on when to use additional node/relationship connections versus additional node properties?
Specifically, I have a need to serialize/save a well-defined data structure to Neo. Imagine I have a Java class. That class has some properties, A, B, C. A and B are primitives, and C is a String-keyed hashmap of complex types that each have five properties, all of which are primitives, that we'll call P1,P2,P3,P4 and P5. Assume there are 10 items in this collection, with keys X1,X2.X10. These values will generally be read only once at application startup, and written very infrequently. Option #1: Create a node, store A and B as properties on that node. Create a node for each object in the hashmap, with a relationship to the previously created node, and set properties on this node corresponding to the key and each of the properties. Option #2: Create a node, store A and B as properties on the node, and store the rest of the data as properties using a naming pattern such as: C.X1.P1, C.X1.P2...C.X10.P5 I guess the core question is, what is the relative cost of storing additional properties and some light parsing versus storing additional relationships and nodes? Option #1 is obviously much more "pure", but at what cost? Thanks, Rick _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
