title: Reliable scheduling with sidekiq
body: <p>I'm building a monitoring service similar to <a href="https://www.pingdom.com" rel="nofollow">pingdom</a> but monitoring different aspects of a system and using <a href="https://github.com/mperham/sidekiq" rel="nofollow">sidekiq</a> to queue the tasks which is working well. What I need to do is to schedule sending out pings every minute, rather than using a cron based system which would require spinning up a new ruby instance every minute I have gone down the route of using <a href="https://github.com/tobiassvn/sidetiq" rel="nofollow">sidetiq</a> (notice the different spelling with a "t") which uses sidekiq's own queue to schedule future tasks. This feels like a neat solution, however I am concerned this may not be the most reliable way of scheduling tasks? If there are issues with the system (as there inevitable will be at some point) will this method of scheduling tasks be less reliable than using a cron based method and why?</p>
  
  <p>Thanks</p>