title: How many requests can a Web API handle concurrently by default
body: <p>I have a very simple Web API developed in c# .Net framework 4.6.<br>
  There are no <code>async</code> calls in entire application. Each request takes around 30 seconds to complete. It does some calculations and returns a JSON string. There is no database involved in this.It just downloads a file from cloud and calculates some values. </p>
  
  <p>It is hosted in Windows Server 2016 , IIS .  </p>
  
  <p>I want to know how many concurrent requests does Web API or IIS handle at a given point of time.    </p>
  
  <p>I know that no of concurrent requests can be increased from web.config like this:</p>
  
  <pre><code>&lt;configuration&gt;
    &lt;system.net&gt;
      &lt;connectionManagement&gt;
        &lt;add address="*" maxconnection="50000"/&gt;
      &lt;/connectionManagement&gt;
    &lt;/system.net&gt;
  &lt;/configuration&gt;
  </code></pre>
  
  <p>Here are some questions I have which I'm sure are very basic.<br>
  1. Does Web API has the capability by default (without adding anything in web.config or anywhere in the application) to handle concurrent requests. If yes, how many?  </p>
  
  <ol start="2">
  <li>Does IIS has the property to handle concurrent requests (using IIS Thread pool) by default. If yes , how many?  </li>
  </ol>
  
  <p>PS: Assuming that all the resources which this API is using are always available.  </p>
  
  <p>It would be very helpful for me if someone can help me understand this and direct me to right articles. Many thanks in advance!</p>