title: Is decoupling web and database tiers via MSMQ necessary or overkill?
body: <p>I'm putting together a simple asp.net web control, that as the result of an ajax form post inserts a record into a MSQL database.</p>
  
  <p>It's possible that the page containing this control will recieve many thousands of hits in a small space of time and I'm worried about the performance issue of opening a database connection, inserting the record and then closing the connection for each request.  </p>
  
  <p>A solution that has occured to me is to make the web control place a message into an MSMQ queue and have a Windows Service on the server periodically read the queue and do a batch insert.</p>
  
  <p>Does that sound like a sensible architecture given that the web and database servers are running on the same machine.  Does it sound necessary?  </p>
  
  <p>From what I've read on the database most of the benefits of using MSMQ are to do with resilience rather than performance, so I might be barking up the wrong tree.</p>
  
  <p>Any advice would be very gratefully appreciated</p>
  
  <p>Many thanks</p>
  
  <p>Pete</p>