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.
Infrastructure as a Service è il nuovo modello che permette di creare delle macchine virtuali all'interno di Windows Azure, senza dover acquistare l'hardware, e senza doverlo gestire. Questo permette di avere un servizio on-demand, che abbatte notevolmente i costi. Durante questa sessione vedremo come creare VM remote e come mettere in comunicazione la propria infrastruttura con quella su Azure.
The first major decision when planning for a Lync deployment is how to deploy Microsoft Lync: as Lync Server 2013 on premises, or Lync Online with Microsoft Office 365 in the cloud. This first decision will shape service quality, resiliency, and resource optimization in your deployment. This session goes over the differences between "on-premise," hybrid, and "on-line" solutions and details situations where each would be optimal for your deployment. Finally, this session covers hosted solutions, the interoperability between Lync and Office 365, and offers guidance in preparing for a potential migration to the cloud.