title: Efficient MySQL database design for a Tinder like app
body: <p>I'm creating an app like Tinder. Which a user can swipe right or like and swipe left or dislike another users. The problem is about storing operations of users. A table is needed for users operations like below</p>
  
  <pre><code>Person 1.   |   Person 2.    |     op
  __________________________________
  000001.          000007.          Dislike
  000001.          000011.          Like
  000001.          000053.          Dislike
  000001.          000173.          Dislike
  </code></pre>
  
  <p>It stores operations and also uses for not showing a user more times. It's ok till now.</p>
  
  <p>But the problem is if just 1000 users swipe another 1000 users that table will have 1M of rows. And if 100,000 users do that...It goes to 100M of rows! Which is very huge.</p>
  
  <p>Do u guys have any idea for a structure designe which not to grow so large?</p>
  
  <p>Thank you.</p>