Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The basic suggestion is to follow <a href="http://en.wikipedia.org/wiki/Representational_State_Transfer" rel="nofollow noreferrer">REST principles</a> and the following points ties some of these principals to the ASP.NET MVC framework:</p> <ol> <li>Make your controllers <a href="http://en.wikipedia.org/wiki/Representational_State_Transfer#Constraints" rel="nofollow noreferrer">stateless</a> - this is more of a '<em>Web</em> performance / scalability' suggestion (as opposed to micro/machine level performance) and a major design decision that would affect your applications future - especially in case it becomes popular or if you need some fault tolerance for example. <ul> <li>Do not use Sessions</li> <li>Do not use tempdata - which uses sessions</li> <li>Do not try to 'cache' everything 'prematurely'.</li> </ul></li> <li>Use <a href="http://www.asp.net/learn/security/tutorial-03-cs.aspx" rel="nofollow noreferrer">Forms Authentication</a> <ul> <li>Keep your frequently accessed sensitive data in the authentication ticket</li> </ul></li> <li>Use cookies for frequently accessed non sensitive information</li> <li>Make your <a href="http://en.wikipedia.org/wiki/Representational_State_Transfer#Constraints" rel="nofollow noreferrer">resources cachable</a> on the web <ul> <li><a href="http://www.google.co.uk/search?q=asp.net%20mvc%20etag" rel="nofollow noreferrer">Utilize ETags</a></li> <li>Use expiration</li> <li>Write your custom ActionResult classes if necessary</li> <li>Utilize <a href="http://en.wikipedia.org/wiki/Reverse_proxy" rel="nofollow noreferrer">reverse proxies</a></li> </ul></li> <li>Compile your JavaScript. <a href="http://code.google.com/closure/compiler/" rel="nofollow noreferrer">There is Closure compiler library</a> to do it as well (sure <a href="http://www.google.co.uk/search?q=javascript%20compiler" rel="nofollow noreferrer">there are others, just search for 'JavaScript compiler'</a> too)</li> <li>Use CDNs (Content Delivery Network) - especially for your large media files and so on.</li> <li>Consider different types of storage for your data, for example, files, key/value stores, etc. - not only SQL Server</li> <li>Last but not least, test your web site for performance</li> </ol>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload