[oak][content model] node tree or property naming convention for structured content

[Nicolas Peltier <np...@adobe.com.INVALID>]

Hi,

I have a use case where a given node has always the same properties I’ll call 1,2,3 for different families I’ll call a,b,c.

The first intuition is to make “folder” nodes with family, so 3 child nodes a,b,c, each one having 1,2,3 properties.

Second intuition I can’t really assess from the yet interesting doc page on segments I’m using [0], is that i would get better performance (size, copy, write, read) if I just create a naming convention, and have a1,a2,a3,b1,… in only one node instead of 4.

I figured I’d ask here first for confirmation / invalidation of my intuitions.

Thanks,
Nicolas

[0] https://jackrabbit.apache.org/oak/docs/nodestore/segment/records.html