In the push to retire Windows XP, application compatibility was all about "getting it over the line," particularly for those who were trying to finish up before the end of support this past April. Now, in a post-XP world, things are changing faster—are your tools, techniques, and processes able to keep up? Do you even want to? And are you able to take full advantage of your platform? Join "The App Compat Guy" for a review of the current state of the art and the secrets of customers who have been able to break the chains and become agile again.
Today we are able to see a clear shift in how enterprises are targeted by malware engineers. The attack landscape has adapted to the new world and they now perform targeted attacks, especially over the social networks. Because guess what? The CEO, CTO, or even the girl next door has a social network account. Join this session and explore how social engineering has grown over time and examine lessons learned from the field on how to best mitigate those traps.
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.