WebSockets has heralded the coming of the real-time web, enabling amazing new experiences in your web browser and connected device. But new paradigms bring new challenges. What about clients that don’t have WebSockets support? How do real-time web features affect the scalability of my web application? How do I organize persistently connected users into logical groups for efficient message delivery? Oh, and make it really, really simple. In this session, learn how ASP.NET SignalR does all this and more.
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.
This session is about migrating an existing Azure Cloud Services based application to Azure Service Fabric. We will begin with a quick discussion on different motivations for such a migration. The rest of the talk will be focused on walking through the migrated application code and discussing the available design choices.