Needing advice for best practices for processing queuded HTTP requests that access a dedicated (non-shared) process

Hi Folks, Most of my experience has been using Visual Studio 2005, so I'm a litlle behind the curve using C# Visual Studio 2013 for process and ASP.Net apps running on Windows Server 2012. I have an existing production app that uses SQL Server for queuing requests and maintaining the status of records submitted to a non-shared process.  I need to revise this app so that the process is invoked by HTTP requests and returns a response either by timing out the process or allowing it to complete.  There will be multiple Windows servers running the dedicated process to support concurrent requests with custom load balancing.
So there are multiple issues I am trying to tackle: 1. I need to service HTTP requests on each server and to return each either as the dedicated process completes or times out. There are some TBDs about utilization and overall capacity planning, but the architecture needs to allow for that.  Each HTTP request to a se ...