title: neo4j - labels vs properties vs relationship + node
body: <p>Any rule of thumb on where to use label vs node property vs relationship + node.</p>
  
  <p>Let's have an example, say I have a store and I want to put my products in neo4j.  Their identifier is the product sku, and I also want to have a categorization on them like this one is for clothes, food, electronics, and you get the idea.  I'll be having a free search on my graph, like the user can search anything, and I'd return all the things related to that search string. </p>
  
  <p>Would it be better to use:</p>
  
  <ol>
  <li>I have a node with <code>sku 001</code>, and I'll tag it a label of <code>Food</code>.</li>
  <li>I have a node with <code>sku 001</code>, and have property on this node called <code>category:"Food"</code></li>
  <li>I have a node with <code>sku 001</code>, and I'll create another node for the <code>Food</code>, and will create a relationship of "<code>category</code>" to relate them.</li>
  </ol>
  
  <p>I have read that if you'll be looking up a property, it's better off as a relationship + node, as traversing is much faster than looking up properties of node.</p>
  
  <p>TIA</p>