title: Handling Long-Running Processes in an ASP.net Web API 2 Service
body: <p>I created a REST service using ASP.net Web API 2.  The service allows a client to POST records which are stored in a SQL Server database.  At this point <em>some other process</em> needs to pull the records from the database, process them, and send the results to another, separate REST service.</p>
  
  <p>Since the processing of the records will be time-consuming, I don't want to perform this step as part of the POST action, but I'm trying to figure out the best approach to designing this <em>other process</em>.</p>
  
  <p>Is there a way to integrate this functionality into the ASP.net REST API project, or is something like a Windows Service the best solution?</p>