title: Multi-threading required in ASP.NET websites?
body: <p>I am building a simple ASP.NET <strong>website</strong>, which will receive SMSes via a 3rd party SMS API (through URL push), and then the website will acknowledge the senders by sending SMSes back to them. I am saving the incoming SMSes in a database. I have implemented the logic as below:</p>
  
  <pre><code>public partial class _Default : System.Web.UI.Page
  {    
      protected void Page_Load(object sender, EventArgs e)
      {
       //declaring variables to be used elsewhere, but in this same class. I have just this one class.  
       //Grabbing the URL parameters here (contents of SMS). 
       //Saving SMSes in the database. Database interaction happening only inside Page_Load. 
        //Call these functions
        SomeLogicFunction();
        SendSMSFunction(); 
      } 
  
      SomeLogicFunction()
      {
      }
  
      SendSMSFunction()
       {
       }
  }
  </code></pre>
  
  <p>Now, I have read somewhere that ASP.NET takes care of multi-threading and similar aspects. So, if I have a simple website like this, do I need to take care of multi-threading? Or Page_Load function/ASP.NET pretty much handles it automatically?  </p>
  
  <p>If the answer is I don't need to do anything, then its all awesome! 
  But if I have to take care of multi-threading, can you please help with some tips on how should I approach? I expect few thousand SMSes. </p>
  
  <p>Thanks. </p>