title: What are the benefits of Asynchronous HTTP
body: <p><strong>Q.1</strong> I know that when we are talking about <code>synchronous HTTP</code>, for each request a Thread may be spawn and get blocked, so when number of simultaneous connections increase, we will encounter massive thread overhead.<br> Asynchronous mode will tolerate some overhead polling responses for something desired, but number of Threads drastically decrease.<br>
  I also know that <code>Asynchronous HTTP</code> will let us take actions even when response delivered is not the complete response (only a part of response is recieved) which is appropriate for real-time actions.<br>
  But what are other benefits of <code>Async HTTP</code>?<br><br>
  <strong>Q.2</strong> I have a server which has only and only one client, but that client will send thousands of requests per second. I use blocking IO (<code>Synchronous HTTP</code>) with lightweight Threads (<code>Quasar</code>). Should I switch to Async? What is the benefit of doing that for me?</p>