title: Polling for database changes: OracleDependency, SignalR, or is that too much?
body: <p>I suppose I'm looking for a best practice, but I've read conflicting information on the various ways to do this. I'm attempting to put together an example of a webpage that contains a grid of information that shows exactly what is in the database. The table could be updated from the webpage via a form, but it could also be updated from various other sources.</p>
  
  <p>How can I go about alerting users to the updates? Here's what I've gone through so far:</p>
  
  <ol>
  <li><p>SignalR could be used to let users "subscribe" to updates on the grid. This would work for the insert/update from the form to the database to alert users. But what about the actual data coming from other non-.NET sources</p></li>
  <li><p>OracleDependency: Callback hits .NET when the DB is updated. I've read this is not good to use on a table that is updated constantly. Why is that? Is this a viable option to hook into SignalR and alert users in the group?</p></li>
  <li><p>Basic polling: Am I overthinking this? Should I simply poll the database on each client, get the changes, and insert into the table via AJAX?</p></li>
  </ol>