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.
With the proliferation of mobile devices as well as the flexibility of delivering mixed topology implementations of Lync, Exchange and other dependent systems, optimizing your security architecture has never been more important. Derek and team will cover: _x000D_ _x000D_ Security Framework: Confidentiality, Integrity and Availability _x000D_ Telecom and network security best practices _x000D_ Trends in authentication: Mobile devices, 2-Factor Authentication _x000D_ Encryption TLS and sRTP_x000D_ Resilient certificate management _x000D_ Mitigating the risk of denial of Service attacks _x000D_ Basic steps for protecting against minute theft _x000D_ Real life edge and reverse proxy scenarios_x000D_