title: Why should I use IoC Container (Autofac, Ninject, Unity etc) for Dependency Injection in ASP.Net Applications?
body: <p>It is kind of theoretical question.</p>
  
  <p>I am already using Unity DY with Service(Facade) pattern on Business layer.
  I is pretty simple to use it but...</p>
  
  <p>there is obviously performance and memory overhead in every small transaction. Instead of creation of DataContext (read it like "sql-connection") i am create several service objects by unity. </p>
  
  <p>Example:
  simple operation "GetAllArticles" cause creation of</p>
  
  <p>Useless:</p>
  
  <ul>
  <li>UserService    (for permission checks)</li>
  <li>ArticleService (for Article Crud operation)</li>
  </ul>
  
  <p>And usefull:</p>
  
  <ul>
  <li>DataContext (for the articleService)</li>
  <li>ArticleViewModels.</li>
  </ul>
  
  <p>But what if is an HightLoadApplication, and billions of people over the world, trying to get article from my super site? What about garbage collector and server's cpu temperature?</p>
  
  <p>So: </p>
  
  <ul>
  <li>Am i understand work with unity(or any other) correct?</li>
  <li>Is there any alternative solutions?</li>
  <li>what should i do in a case of highload application</li>
  </ul>
  
  <p>I will be happy to hear your opinion and experience, even if it is not panacea or "best practice".</p>