When designing cloud applications, you should take into account the fact that a failure or malfunction of any component of the system is possible. This template is called Designing for Failure. This design approach helps minimize the negative consequences of failure of any component of the internal or external system. Sometimes, it is not so simple to use the Designing for Failure template, but the Azure platform greatly facilitates this task due to the fact that some of the functions are implemented by cloud services—Azure Web Sites, Traffic Manager, CDN, RA—Geo Redundant Storage. During this session, we shall talk about how to use the functionality provided by Azure to ensure the accessibility of a website, even in the event of failure of one of the regions of the platform.
In this session the speaker will go through the various uses of Windows Azure for dev and test scenarios. The content wil call out common current day flaws in testing, such as don't test at all, poor/incomplete hardware, out of date builds in QA, can't test to scale, and several other scenarios. The demo in this session will include building/deploying a simple ASP.Net MVC4 app for testing.
Come hear the master of Windows troubleshooting, walk you step-by-step through how he has solved seemingly unsolvable system and application problems on Windows. With all new real case studies, Mark shows how to apply the Microsoft Debugging Tools and his own Sysinternals tools, including Process Explorer, Process Monitor, to solve system crashes, process hangs, security vulnerabilities, DLL conflicts, permissions problems, registry misconfiguration, network hangs, and file system issues. These tools are used on a daily basis by Microsoft Product Support and have been used effectively to solve a wide variety of desktop and server issues, so being familiar with their operation and application will assist you in dealing with different problems on Windows.