title: ORM vs traditional database query, which are their fields?
body: <p>ORM seems to be a fast-growing model, with both pros and cons in their side. From Ultra-Fast ASP.NET of Richard Kiessig (<a href="https://rads.stackoverflow.com/amzn/click/com/1430223839" rel="noreferrer" rel="nofollow noreferrer">http://www.amazon.com/Ultra-Fast-ASP-NET-Build-Ultra-Scalable-Server/dp/1430223839/ref=pd_bxgy_b_text_b</a>):</p>
  
  <p>"I love them because they allow me to develop small, proof-of-concept sites extremely quickly. I can side step much of the SQL and related complexity that I would otherwise need and focus on the objects, business logic and presentation. However, at the same time, I also don't care for them because, unfortunately, their performance and scalability is usually very poor, even when they're integrated with a comprehensive caching system (the reason for that becomes clear when you realize that when properly configured, SQL Server itself is really just a big data cache"</p>
  
  <p>My questions are:</p>
  
  <ul>
  <li><p>What is your comment about Richard's idea. Do you agree with him or not? If not, please tell why.</p></li>
  <li><p>What is the best suitable fields for ORM and traditional database query? in other words, where you should use ORM and where you should use traditional database query :), which kind/size... of applications you should undoubtedly choose ORM/traditional database query </p></li>
  </ul>
  
  <p>Thanks in advance</p>