title: Tracking User activity log - SQL vs NoSQL?
body: <p>I have a mysql database containing tables like <strong>User, playlist, videos, tags</strong>.  </p>
  
  <p>Based on this I would like to collect the user activity on the application. the example use cases may be :   </p>
  
  <pre><code>a.) (user) joined (app) on (date)  
  b.) (user) created playlist (playlist) on (date)  
  c.) (user) added (video(s)) to playlist (playlist)  
  d.) (user) added tags (tag(s)) to video in playlist (playlist)  
  </code></pre>
  
  <p>Given such data, which would be better alternative to design a user activity schema? <code>relational(I am using MySQL) or NoSQL(non-relational, like MongoDB)</code>  </p>
  
  <p><strong>Favoring NoSQL</strong><br>
  a.) The other thing is since activity lit will be huge, retrieving data should be fast, I read Document Oriented database performs well in such scenarios since no joining between the tables is needed<br>
  b.) Since the activity log may contain no,one,many variables depending upon the activity happening, a relational schema might not be a good solution.   </p>
  
  <p>I would like to learn more about it, please share the knowledge <code>:)</code><br>
  Thank you</p>