title: ASP.NET, IIS and COM
body: <p>I'm not that familiar with COM and was hoping that someone out there, who is, could help verify what I have below is correct.</p>
  
  <p>If I have two completely separate Requests (request 1 &amp; request 2), then this creates two separate instances of my WebApplication.  So far so boring.  </p>
  
  <p>If each instance then contacts the SAME web service, then presumably two instances of the Web Service are also instantiated.  </p>
  
  <p>This is where it gets interesting.</p>
  
  <p>These web services create a .NET assembly which then references an in-process (registered via regsvr32) COM-dll (via Interop).</p>
  
  <p>Is my diagram correct?  </p>
  
  <p><img src="https://i.stack.imgur.com/CuVik.png" alt="alt text"></p>
  
  <p>This COM-DLL connects to the database, performs a query, returns data to the web service which then returns the data in JSON to the client.  All done AJAXy.</p>
  
  <p>The other question I have is - is this okay performance-wise?  I don't see why it shouldn't scale, and be able to return data to the user </p>