title: SQL vs. NoSQL database for 'tags-heavy' CRM application
body: <p>I'm building a talent management CRM application and I'm having trouble choosing between a SQL or NoSQL database for my data. </p>
  
  <p>The application will only have a few 'core' entities (Person, Job, Company, Interview), and will rely heavily on 'tagging' of those entities. You can add Tags and Notes to a Person, a Job, a Company, and then sort/search data by those tags.</p>
  
  <p>What I learned about NoSQL is that I can just have a Person object (document) with an array of Tags and Notes, where in SQL I would need separate Tags and Notes tables and construct joins to gather all my data for a Person.</p>
  
  <p>Could anyone give me some pointers on what would be the way to go for my particular scenario?</p>
  
  <p>Thanks!</p>