Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>If you can develop for .NET 4 Framework then you can decouple by using F# or the Parallel Computing features (<a href="http://msdn.microsoft.com/en-us/library/dd460693(VS.100).aspx" rel="nofollow noreferrer">http://msdn.microsoft.com/en-us/library/dd460693(VS.100).aspx</a>)</p> <p>F# is designed to support parallel computing so it may be a better choice than moving code into services. </p> <p>Though, if you wanted, you could just use WCF and off-load everything to webservices, but that may not really solve your problem as it just moves the issues elsewhere.</p> <p>EDIT: Moving the non-essential to webservices may make the most sense then, and this is a standard practice where the webserver is outside of the firewall, so vulnerable, so all the real work is done by other servers, and the webserver is just responsible for static pages and rendering. </p> <p>You can use Spring.NET for this, if you don't want to add webservices, but either way you are largely just calling a remote process to do the work.</p> <p>This is scalable as you can separate the business logic to several different servers, and since the webserver is largely just the view part of MVC it can handle more requests than if all the MVC work is in the webserver.</p> <p>Because it is designed for this, Spring.NET should be easier to test, but, webservices can also be tested, as you should test each part separately, then do functional tests, but, by using Spring.NET it is easier to mock out levels.</p>
 

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