При создании облачных приложений необходимо стараться всегда их проектировать с учетом того, что в любом компоненте системы возможен отказ или сбой в работе. Это так называемый шаблон «Designing for failure». Подобный подход при проектировании позволяет минимизировать негативные последствия отказа какой-либо части внутренней или внешней системы. Проектировать с учетом «Designing for failure» не всегда просто, но платформа Azure во многом облегчают эту задачу за счет того, что часть функциональности реализуется облачными службами платформы - Azure Web Sites, Traffic Manager, CDN, RA - Geo Redundant Storage. В данной сессии будет рассказано о том, как использовать возможности платформы Azure для обеспечения доступности сайта, даже в случае выхода из строя одного из регионов платформы.
Sochi 2014 Olympic and Paralympic Winter Games were undoubtedly the most important sporting event of 2014. During the Games, the official website of the Games became the most popular sports website in the world. We shall take a look under the hood and analyze its distributed architecture organically built on Microsoft Azure in order to cope with the rapidly growing and unpredictable load. Come and learn about the interesting problems we faced, as well as about how we designed our system in accordance with the strict requirements for this class of solutions.
Publishing Exchange used to be easy. You installed Microsoft Security and Acceleration (ISA) Server or Forefront Threat Management Gateway (TMG) and considered your work done. But with the changes in roadmap of Microsoft security products such as TMG and UAG, and the addition of features like ARR and WAP, the sea of TLAs has become more complex than ever. Come and learn what the real risks are when publishing Exchange to the Internet, what your choices are, which you should choose, and how to deploy them. There's a TLA for everyone when it comes to publishing Exchange, but make sure you know which is which and which one you need, if at all. The Windows team have added an additional component called Application Request Routing 3.0 to the Internet Information Service (IIS) role, which enables IIS to handle reverse proxy requests and also perform layer seven Load Balancing of these requests.
SharePoint consultants and developers work in projects, and most SharePoint environments are large. As a best practice, the development and test environments should be as equal as possible to the production environment. In reality, SharePoint development and test environments are not as equal as possible. Based on Microsoft Azure Infrastructure as a Service (IaaS), we have a chance to get the environment as equal as possible and to speed up projects and reduce project cost from planning through final deployment of hardware requirements on production environments. Consultants can act faster, or shall we say "very fast". This session demonstrates how to use the Microsoft Azure Management Portal, Windows PowerShell or Microsoft System Center to manage many environments like SharePoint farms in Azure and to deploy the 1-n farms via script, to manage more than 100 cores and terra bytes of VHDs on-demand. Learn how to scale your SharePoint environment up and down, and switch off all resources to scale based on your needs on-demand. Learn to load test on-demand in SharePoint on Azure, for better quality in your production environment. At the end of the Session, you'll understand the latest thinking on Infrastructure as a Service for SharePoint, and the difference from standard hosting. We also discuss how to design a SharePoint Farm for Azure IaaS for Scale-up/-down, and out and off. Focusing on SharePoint and SQL Server and BI, we demonstrate the mechanism to enroll large environments in minutes and to bring them into a very low-cost state for non-business hours, based on demand. With this thinking, IT environments like SharePoint are designed for high availability. At the end of session you'll see the cloud and Azure from a new perspective, and see that hosting is not all the time 24x7, with high availability.