title: Meteor oplog tailing and performance
body: <p>What are the advantages of using oplog tailing with Meteor? 
  I know of these:</p>
  
  <ul>
  <li>Having replica sets ensures high availability</li>
  <li>Oplog tailing gives improved performance when it comes to detecting changes in the DB and pushing these to the clients</li>
  </ul>
  
  <p>More specifically, given a Meteor app where the ‘real-time’ aspect isn’t that important (i.e. not write intensive enough that a client is likely to see any data changing during their session) and also ignoring the availability advantages of having replica sets, are there any other advantages of using oplog tailing?</p>