REDIS
http://highscalability.com/blog/2014/9/8/how-twitter-uses-redis-to-scale-105tb-ram-39mm-qps-10000-ins.html
Still good to read:
Scale up and Scale out
http://www.codinghorror.com/blog/2009/06/scaling-up-vs-scaling-out-hidden-costs.html
Performance - Good Start:
http://stackoverflow.com/questions/2246251/how-to-improve-asp-net-mvc-application-performance
Integration Test
For web applications, the most common approach to integration testing is UI automation. This term
refers to simulating or automating a web browser to exercise the application’s entire technology stack by
reproducing the actions that a user would perform, such as clicking buttons, following links, and
submitting forms.
The following are the two best-known open source browser automation options for .NET
developers:
• Selenium RC (http://seleniumhq.org/), which consists of a Java “server”
application that can send automation commands to Internet Explorer, Firefox,
Safari, or Opera, plus clients for .NET, Python, Ruby, and multiple others so that
you can write test scripts in the language of your choice. Selenium is powerful and
mature; its only drawback is that you have to run its Java server.
• WatiN (http://watin.sourceforge.net/), a .NET library that can send automation
commands to Internet Explorer or Firefox. Its API isn’t as powerful as Selenium,
but it comfortably handles most common scenarios and is easy to set up (you
need to reference only a single dynamic-link library).
View
In the view, you can access WebPageRenderingBase directly, e.g. get user name - @User.Identity.Name
Server Debugging Tools
- Dumpchk - check dump
- winDbg - hang or crash
- vmMap - memory leaking
- Fuslogvm - assembly binding (Link)
